7 ms·
Just goes to show how much a single SQL server can scale before having to worry about sharing and horizontal scaling
by jarym 6y ago
Just goes to show how much a single SQL server can scale before having to worry about sharing and horizontal scaling
- ed25519FUUU 6y agoThis is especially true with your own hardware. Trying this kind of thing in the cloud is usually prohibitively expensive.
- jbverschoor 6y agoIt’s doesn’t have to. Unless you’re conditioned to believe that aws is cheap
- deleted 6y ago[deleted]
- ed25519FUUU 6y agoI'm curious what the cost would be to run this type of hardware at any cloud vendor? Does it even exist?
- jeffbee 6y agoThat's the wrong way to think about the cloud. A better way to think about it would be "how much database traffic (and storage) can I serve from Cloud Whatever for $xxx". Then you need to think about what your realistic effective utilization would be. This server has 153600 GB of raw storage. That kind of storage would cost you $46000 (retail) in Cloud Spanner every month, but I doubt that's the right comparison. The right math would probably be that they have 250 million customers and perhaps 1KB of real information per customer. Now the question becomes why you would ever buy 24×6400 GB of flash memory to store this scale of data.
- whitepoplar 6y agoNot completely comparable, but Hetzner offers the following dedicated server that costs 637 euro/month (maxed out): - 32-core AMD EPYC - 512GB ECC memory - 8x 3.84TB NVMe datacenter drives - Unmetered 1gbps bandwidth
- dastbe 6y ago(I work at AWS, but this is just for fun) Checking out AWS side, the closest I think you'd get is the x1.32xlarge, which would translate to 128 vCPU (which on intel generally means 64 physical cores) and close to 2TB of RAM. nvme storage is only a paltry 4TB, so you'd have to make up the rest with EBS volumes. You'd also get a lower clock speed than they are getting out of the EPICs
- WatchDog 6y agoIf you eschew RDS, the largest you can go up to seems to be a u-24tb1.metal. 448 vcpu, 24TiB of RAM, $70 an hour. ~$52k per month.
- Aeolun 6y agoOh, only $70 per hour. I think I can start that for an hour or so before my wallet is exhausted :P
- ficklepickle 6y agoI spun up a 32 vCore spot instance to crack my own WiFi password once. It only cost ~$2 and I felt so powerful.
- PeterCorless 6y agospittakes reading the suggestion of replacing NVMe with EBS I mean, yeah, I guess you can. But a lot depends on your use case and SLA. If you need to keep ultra-low p99s — single digits — then EBS is not a real option. But if you don't mind latencies, then yeah, fine. Don't get me wrong: EBS is great. But it's not a panacea and strikes me as a mismatch for a high performance monster system. If you need NVMe, you need NVMe.
- dastbe 6y agoIt wasn't a suggestion of replacement, it was saying that even the closest instance still doesn't get you 24TB of on-host storage, having to use EBS instead.
- cperciva 6y agoBased on their stated 225M sites and a renewal period of 90 days, they're probably averaging around 40 certificates per second. That's only an order of magnitude higher than bitcoin; I wouldn't call it an indication of an ability to scale to a particularly large amount of traffic.
- RL_Quine 6y agoBitcoin is ECDSA verification, letsencrypt is generating RSA signatures, the two aren't even remotely comparable.
- schoen 6y agoBut the cryptographic bottleneck is in HSMs, not in database servers (database servers don't generate the digital signatures, they just have to store them after they've been generated).
- SulfurHexaFluri 6y agoBitcoin is actually not limited by compute power at all. Its an artificial cap on transaction rate to prevent the blockchain from expanding too large and preventing normal users from hosting the whole thing. You can see the blockchain size was growing exponentially but then switches to linear as we hit the transaction cap and it now sits at about 350GB
- tyingq 6y agoDoes "certbot renew" talk to the mothership at all if no certs are ready for renewal? If it does, most setups I've seen run the renewal once or twice a day since it only does the renew when you're down to 30 days left. There may also be some OCSP related traffic.
- mike_d 6y agoCertbot will look at the expiration timestamp on your local certs without talking to Lets Encrypt.
- nine_k 6y agoRead performance is much easier to scale (in one box or several) than write performance. It's usually the writes that make you look at Cassandra and similar, instead of adding more disks and RAM, or spinning another read-only replica. 24 NVMEs should have a lot of write throughput, though.