3 ms·

What's so wrong with that model?

• ComputerGuru 6y ago
  It doesn’t scale and makes some abstractions more difficult.
  • claytonjy 6y ago
    how about pgBouncer for connection pooling? I know it's more operational overhead, but is that still not good enough for your use case?
  • ComodoHacker 6y ago
    How far does it need to scale? Times of two-tier apps are gone, middle tier has it's own pooling.
    • pgaddict 6y ago
      Ideally thousands (and maybe even tens of thousands) of connections. At the moment we're quite far from that, as the benchmarks in the thread [1] demonstrate (low hundreds, I'd say). There's an awful lot of applications designed with the idea that connections are cheap. And on some databases it's actually true. But it's also about hardware - machines with hundreds of cores are getting quite common, applications have "think time" so you need to use a multiple of core count to saturate the CPU, etc. Currently the limit is probably "low hundreds" depending on the workload (the shorter/cheaper the transactions, the worse). Connection pools are great, but unfortunately not really a universal solution. [1] https://www.postgresql.org/message-id/flat/20200301083601.ews6hz5dduc3w2se%40alap3.anarazel.de https://www.postgresql.org/message-id/flat/20200301083601.ew...