Feedback-ID: i76984098:Fastmail
Message-ID: <226c7ab6-5c4e-4b98-8fd5-2d5edee7e4e9@aklaver.com>
Date: Thu, 22 Jan 2026 08:28:02 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Pgbouncer performance query
To: KK CHN <kkchn.in@gmail.com>, pgsql-general <pgsql-general@postgresql.org>
References: <CAKgGyB_fxnmsMq-a4KxH+PQjL6_5m14UvpEb5ejbuiJy7H_iFA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAKgGyB_fxnmsMq-a4KxH+PQjL6_5m14UvpEb5ejbuiJy7H_iFA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/226c7ab6-5c4e-4b98-8fd5-2d5edee7e4e9%40aklaver.com>
Precedence: bulk

On 1/22/26 04:35, KK CHN wrote:
> List,
> 
> I am trying pgbouncer  for inhouse deployment for PostgreSQL 16.
> 
> My setup is      PostgreSQL VM : 5444 <=> Pgbouncer VM:5444  <===> Clients
> (PostgreSQL with IP 10.12.0.2  and  Pgbouncer 10.12.0.35 )
> 
> Conducted an inhouse  benchmark  test (pgbench) performed,   I have seen 
> the following results.
> 
> On direct hit  the DB server  handled tps = 162252.508744 (without 
> initial connection time)
> latency average = 1.233 ms  (Total time taken around  2 Minutes  to 
> complete)
> Through Pgbouncer  it handled  tps = 25107.166425 only  
> ( without initial connection time)
> latency average = 11.949 ms   ( Total time taken around 20 Minutes to 
> complete )
> 
> Could someone shed some light on   improving the total time taken by 
> pgbouncer in this scenario ?     How can I improve the  total time 
> taken  from 20 Minutes to any reasonably good value, say 5 Minutes is it 
> possible  ?

The significant difference between the test setups is the introduction 
of an additional VM between the clients and the database server in the 
pgBouncer case.

Have you tried it with pgBouncer installed in the Postgres VM?

Also see:

https://www.pgbouncer.org/faq.html#should-pgbouncer-be-installed-on-the-web-server-or-database-server

-- 
Adrian Klaver
adrian.klaver@aklaver.com