[mozumder]

I'd like to see this data on Postgres scaling updated, with more info on the write scaling as well. (the chart appears to be for SELECT queries only)

[brianwawok]

The other change is now a single select can use multiple cores, so you could see how that scaled to 32, 64, 128 cores...

[qaq]

On highly concurrent PG systems by when using parallel queries you are sacrificing throughput for better latency. You really don't want to use more than a fairly small number of workers per single select.

[qaq]

Outside of some very exotic scenarios you are IOPS bound on writes and not CPU bound.

[mozumder]

Is that still a problem with cheap NVMe drives that can do 500k IOPS?

[Tostino]

Not a problem at all if you provision your server properly so you aren't IOPS bound, though there are plenty of databases which simply won't fit on NVMe drives, so in those cases, yes it could still be a problem.

[user5994461]

Not likely to be a problem if you have FusionIO drives. Likely to be a problem sooner or later on everything else. A definitive recurrent issues on all cloud providers and NAS/network drives.

[qaq]

Nope but everyone is running in the "cloud" and there you are lucky to get 50K IOPS

[mozumder]

This is one of the reasons I don't run in the cloud.

[qaq]

same here