public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jorge Batista <[email protected]>
To: Raj <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: RE: TPS in direct Postgres Vs TPS in pgbouncer
Date: Sun, 21 Jun 2026 14:37:06 +0000
Message-ID: <BL1PR18MB4165C856E8D17BB6C5A4DE7BD6E02@BL1PR18MB4165.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJk5AtYBpy2ROKzv+se+LXpM4PZdzifnY_rZvamjHpBELxYUog@mail.gmail.com>
References: <CAJk5AtYBpy2ROKzv+se+LXpM4PZdzifnY_rZvamjHpBELxYUog@mail.gmail.com>
Raj, when you turned on pgbouncer, did you check if it's set to "transaction mode" & not "session mode"?
Also worth checking if pgbouncer itself is maxing out a CPU core during the slow test, both are common causes of a TPS drop like that, separate from Postgres itself.
Regards,
jorge batista
From: Raj <[email protected]>
Sent: Sunday, June 21, 2026 9:25 AM
To: Pgsql-admin <[email protected]>
Subject: TPS in direct Postgres Vs TPS in pgbouncer
EXTERNAL: This email originated from outside of our organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi All,
When the application team is using posytgres directly for 17.9 version, they get necessary TPS.
When they use pgbouncer, they get 50% reduction in TPS.
What are general advices?
My set up is 3 node PATRONI, where node3 is DR and manual failover.
Two nodes (node1 and node2) are in site A ..having haproxy, pgnouncer is bound with haproxy.
________________________________
Notice: This e-mail is intended only for the named person or entity to which it is addressed and contains valuable business information that is privileged, confidential and/or otherwise protected from disclosure. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee, or agent responsible for delivering the message to the intended recipient, is strictly prohibited. All contents are the copyright property of the sender. If you are not the intended recipient, you are nevertheless bound to respect the sender's worldwide legal rights. We require that unintended recipients delete the e-mail and destroy all electronic copies in their system, retaining no copies in any media. If you have received this e-mail in error, please immediately notify us by returning the e-mail to the sender. We appreciate your cooperation.
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: RE: TPS in direct Postgres Vs TPS in pgbouncer
In-Reply-To: <BL1PR18MB4165C856E8D17BB6C5A4DE7BD6E02@BL1PR18MB4165.namprd18.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox