Re:Updating a 50 terabyte PostgreSQL database (2018)
by gdgdgdgbgfff on Monday March 22, 2021 @05:39AM
(#26538577)
Vertical scaling like this will have quite a few physical limits, eg max cores (is it 64?). I would think that they may be fast approaching these limits?. For a an scalable enterprise solution would it not be better, and also more cost-efficient, to horizontally scale. Shard the tables over many nodes.
[ Parent
| on HN ]
Re:Updating a 50 terabyte PostgreSQL database (2018)
by jnwatson on Monday March 22, 2021 @08:00AM
(#26539609)
You can buy boxes with 30x more RAM without going super boutique. You can buy quad-socket server motherboards, so you can have 64x4 cores.
For the vast majority of businesses, vertical scaling is quite feasible.
Re:Updating a 50 terabyte PostgreSQL database (2018)
by noir_lord on Monday March 22, 2021 @08:15AM
(#26539745)
128x4 (EPYC 7000 series go up to 128) assuming you can get a 4 socket board.
Re:Updating a 50 terabyte PostgreSQL database (2018)
by gdgdgdgbgfff on Monday March 22, 2021 @08:28AM
(#26539844)
I thought 64 cores was a limit coming from Postgres
http://rhaas.blogspot.com/2012/04/did-i-say-32-cores-how-abo...
Re:Updating a 50 terabyte PostgreSQL database (2018)
by kasey_junk on Monday March 22, 2021 @09:41AM
(#26540632)
That’s a 10 year old restriction. At least as of Postgres 9.2 you could run more than 64 cores (though Postgres didn’t always use them effectively).
Re:Updating a 50 terabyte PostgreSQL database (2018)
by darksaints on Monday March 22, 2021 @09:37AM
(#26540573)
I would think it is a bit higher now, as this benchmark is for a pretty old version that's not even supported anymore. In particular, I'm pretty sure that shared memory throughput is a major factor for scaling the number of cores, and there have been quite a few changes to the shared memory subsystem since then. But even then, there probably are some significant overheads that are reached before you get to the limits of single node systems that are available today.