Re: How to keep queries low latency as concurrency increases
От | Greg Williamson |
---|---|
Тема | Re: How to keep queries low latency as concurrency increases |
Дата | |
Msg-id | 1351635114.18993.YahooMailNeo@web125906.mail.ne1.yahoo.com обсуждение исходный текст |
Ответ на | Re: How to keep queries low latency as concurrency increases (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: How to keep queries low latency as concurrency increases
|
Список | pgsql-performance |
Jeff / Catalin -- Jeff Janes wrote: >On Mon, Oct 29, 2012 at 5:11 PM, Catalin Iacob <iacobcatalin@gmail.com> wrote: > >> pgbouncer 1.4.2 installed from Ubuntu's packages on the same machine >> as Postgres. Django connects via TCP/IP to pgbouncer (it does one >> connection and one transaction per request) and pgbouncer keeps >> connections open to Postgres via Unix socket. > >Isn't pgbouncer single-threaded? > >If you hitting it with tiny queries as fast as possible from 20 >connections, I would think that it would become the bottleneck. > >Cheers, > I'm sure pgbouncer has some threshold where it breaks down, but we have servers (postgres 8.4 and 9.1) with connections fromruntime (fed via haproxy) to pgbouncer that routinely have tens of thousands of connections in but only 40-70 postgresconnections to the postgres cluster itself. Mix of queries but most are simple. Typically a few thousand queriesa second to the readonly boxes, about the same to a beefier read / write master. This is a slightly old pgbouncer at that ... used is a fairly basic mode. Greg Williamson
В списке pgsql-performance по дате отправления: