Pgagroal: High-performance connection pool for PostgreSQL
1–10 of 39 posts
Re: Pgagroal: High-performance connection pool for PostgreSQL
#2and all that just because Postgresql team doesn't want to use threads/tasks instead of heavy processes... I don't know any other DBMS that require an additional infrastructure layer just for connection pooling.
Re: Pgagroal: High-performance connection pool for PostgreSQL
#3I'm curious, does anyone know how this compares to Yandex Odyssey or Pgpool?
Re: Pgagroal: High-performance connection pool for PostgreSQL
#4"PostgreSQL's model of one process per connection doesn't scale, so let's build a connection pooler that uses one process per connection."
Certainly sounds like a strange concept. How well does it scale with thousands of connections?
Re: Pgagroal: High-performance connection pool for PostgreSQL
#5"PostgreSQL's model of one process per connection doesn't scale, so let's build a connection pooler that uses one process per connection." Certainly sounds like a strange concept. How well does it scale with thousands of connections?
Not the author but PG connection scalability being blamed on per-process model is somewhat misunderstood. You can easily have many hundreds of thousands of processes, they are mostly equivalent to threads on Linux anyway (with some minor differences ofc).
Instead the poor scalability stems from the amount of resources allocated to each connection. If postgres was to switch to threads without changing this architecture it's likely scalability wouldn't be majorly improved.
By the same token a connection pooler that is fork based but only allocates a very small amount of resources per connection is still likely to a net win as it can do statement based pooling of a smaller number of postgres connections.
Re: Pgagroal: High-performance connection pool for PostgreSQL
#6> Pronounced: p-g-a-gro-al, named after Agroal in Portugal.
Interesting!
Re: Pgagroal: High-performance connection pool for PostgreSQL
#7I'd love to read a comparison with PgBouncer (I assume that PgBouncer is still the dominant connection pool)
Re: Pgagroal: High-performance connection pool for PostgreSQL
#8> Pronounced: p-g-a-gro-al, named after Agroal in Portugal. Interesting!
Sorry but that's clearly p-gag-roll, whatever the creators may wish.
Re: Pgagroal: High-performance connection pool for PostgreSQL
#9> This report describe pgagroal in relationship to 3 other PostgreSQL connection pool implementations, which we will call "a", "b" and "c".
Why? Just why! Please put up names rather than saving faces for other poolers!
Re: Pgagroal: High-performance connection pool for PostgreSQL
#10> This report describe pgagroal in relationship to 3 other PostgreSQL connection pool implementations, which we will call "a", "b" and "c". Why? Just why! Please put up names rather than saving faces for other poolers!
Also make the benchmark code open source, so that we can run it on our own hardware and judge it's relevancy.