Parler Hosting Requirements
twitter.com
Parler Hosting Requirements
1–10 of 31 posts
Re: Parler Hosting Requirements
#2Copying their requirements as text (original grammar preserved, including GB and Gb confusions).
It's a good glimpse of what unlimited cloud budget does to companies. I quote:
"""
* 40x i3.Metal instances (64 vCPU's, 512 Gb ram (more ram, of course, better for those)), 14 Tb nVME e/a (Scylla cluster)
* 70-100x (96 vCPUs, 768 GB RAM) - 4 Tb nVME e/a (PSQL cluster, could use more RAM and CPU, but not easy to get)
* 300-400 various other instances, less picky, generally 8-16 cores w/ 32-64 Gb of ram as available
* Internal traffic ~300-400 Gb of traffic/minute
* External traffic ~100-120 Gb of traffic/minute
"""
Re: Parler Hosting Requirements
#3I have said it before, I will say it again: Own your infrastructure.
Re: Parler Hosting Requirements
#4Copying their requirements as text (original grammar preserved, including GB and Gb confusions). It's a good glimpse of what unlimited cloud budget does to companies. I quote: """ * 40x i3.Metal instances (64 vCPU's, 512 Gb ram (more ram, of course, better for those)), 14 Tb nVME e/a (Scylla cluster) * 70-100x (96 vCPUs, 768 GB RAM) - 4 Tb nVME e/a (PSQL cluster, could use more RAM and CPU, but not easy to get) * 300…
Wait, is this a joke? This sounds like the worst built infrastructure I've ever heard of where they had more money than engineering sense.
Also, Gbpm.
Re: Parler Hosting Requirements
#5Copying their requirements as text (original grammar preserved, including GB and Gb confusions). It's a good glimpse of what unlimited cloud budget does to companies. I quote: """ * 40x i3.Metal instances (64 vCPU's, 512 Gb ram (more ram, of course, better for those)), 14 Tb nVME e/a (Scylla cluster) * 70-100x (96 vCPUs, 768 GB RAM) - 4 Tb nVME e/a (PSQL cluster, could use more RAM and CPU, but not easy to get) * 300…
Wait, is this a joke? This sounds like the worst built infrastructure I've ever heard of where they had more money than engineering sense. Also, Gbpm.
I don't believe it's a joke. It still might be a deliberate lie (a random twit is not a real source of knowledge), but so far this is consistent with what we already know. See https://news.ycombinator.com/item?id=25769730
Re: Parler Hosting Requirements
#6I have said it before, I will say it again: Own your infrastructure.
That doesn't solve the the software/architecture problems that led to these huge hosting requirements.
Re: Parler Hosting Requirements
#7I have said it before, I will say it again: Own your infrastructure.
> Own your infrastructure.
Absolutely. I have also said this countless times before in relation to self-hosted git. [0] Each time GitHub went down every week last year, I have made the case against the 'centralising everything' argument.
The social networks that didn't survive de-platforming are the ones that didn't self host. Parler is on that list.
Re: Parler Hosting Requirements
#8I have said it before, I will say it again: Own your infrastructure.
It's hard to "own your infrastructure" when you needs are so extreme. Part of the job of tech workers is to make things efficient so that the company doesn't end up with an outsized OpEx or CapEx. With all this hardware required, they have made it impossible to own their own hardware.
Re: Parler Hosting Requirements
#9Gigabit per minute? Do they have a single knowledgeable networking architect on staff?
Why not just measure things in random-sized-image-files-per-full-moon?
Re: Parler Hosting Requirements
#10Given that they forgot to strip EXIF data I’m going to go with there being something completely absurd behind this.
Actually that might be it. If they didn’t strip metadata then maybe they’re shuffling around all images and videos in whatever format and quality they got it? ie one big data lake of mystery content so to speak