> The use case is not representative of a real-life scenario, so the value of the presented results are minimal.

Maybe I'm reading the article wrong, but it is representative of any application that uses a PosgreSQL server for data, correct?

In what way is that not a real-life scenario? I've deployed Single monolith + PostgreSQL to about 8 different clients in the last 2.5 years. It's my largest source of income.

▲

Implicated 2 hours ago | parent | next [-]

> I've deployed Single monolith + PostgreSQL to about 8 different clients in the last 2.5 years. It's my largest source of income.

And... do you do that with the default configuration?

▲

lelanthran 2 hours ago | parent [-]

> And... do you do that with the default configuration?

Yes. Internal apps/LoB apps for a large company might have, at most 5k users. PostgreSQL seems to manage it fine, none of my metrics are showing high latencies even when all employees log on in the morning during the same 30m period.

	▲	Implicated 2 hours ago \| parent [-]
		I'm definitely getting the wrong kind of clients. Kudos to you sir. Sincerely, I'm not hating, I'm actually jealous of the environment being that mellow.

▲

m000 3 hours ago | parent | prev [-]

When you run a relational database, you typically do it for the joins, aggregations, subqueries, etc. So a real-life scenario would include some application actually putting some stress on postgres.

If your don't mind overprovisioning your postgres, yes I guess the presented benchmarks are kind of representative. But they also don't add anything that you didn't know without reading the article.

	▲	lelanthran 2 hours ago \| parent [-]
		> If your don't mind overprovisioning your postgres Why would I mind it? I'm not using overpriced hosted PostgreSQL, after all.