Re: How to keep queries low latency as concurrency increases

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Catalin Iacob <iacobcatalin(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: How to keep queries low latency as concurrency increases
Date: 2012-10-30 21:58:33
Message-ID: CAMkU=1zq_pOG19tdq0UGoCNr71ojw5RpqUXXAjwR-K83J9zdTA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Oct 29, 2012 at 5:11 PM, Catalin Iacob <iacobcatalin(at)gmail(dot)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,

Jeff

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Williamson 2012-10-30 22:11:54 Re: How to keep queries low latency as concurrency increases
Previous Message Jon Nelson 2012-10-30 21:31:20 Re: set-returning calls and overhead