On 27.02.2021 20:40, AJG wrote:
Hi,
Greatly appreciate if you could please reply to the following questions as
time allows.
I have seen previous discussion/patches on a built-in connection pooler. How
does this scalability improvement, particularly idle connection improvements
etc, affect that built-in pooler need, if any?
Same general question about an external connection pooler in general in
Production? Still required to route to different servers but no longer
needed for the pooling part. as an example.
Many Thanks!
Connection pooler is still needed.
The patch for GetSnapshotData() mostly improves scalability of read-only
queries and reduce contention for procarray lock.
But read-write upload cause contention for many other resources:
relation extension lock, buffer locks, tuple locks and so on.
If you run pgbench at NUMA machine with hundreds of cores, then you will
still observe significant degradation of performance with increasing
number of connection.
And this degradation will be dramatic if you replace some non-uniform
distribution of keys, for example Zipfian distribution.
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
