Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjMCr-00Dceb-2N for pgsql-general@arkaria.postgresql.org; Fri, 23 Jan 2026 18:48:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vjMCq-00191b-0x for pgsql-general@arkaria.postgresql.org; Fri, 23 Jan 2026 18:48:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vjMCp-00191R-17 for pgsql-general@lists.postgresql.org; Fri, 23 Jan 2026 18:48:28 +0000 Received: from fhigh-a6-smtp.messagingengine.com ([103.168.172.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vjMCm-000000007GB-08nq for pgsql-general@postgresql.org; Fri, 23 Jan 2026 18:48:27 +0000 Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.phl.internal (Postfix) with ESMTP id C834D140009A; Fri, 23 Jan 2026 13:48:21 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Fri, 23 Jan 2026 13:48:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1769194101; x=1769280501; bh=hXPb+QrHCUgPPrXiacLZuddFplhPGYJSE5iT/NXvgHE=; b= Y54yKcK0Sqq4fjkHdtqmUas/IKib4EoL8exgYEzL5AJg5Wb9fgm62wXwskkC9eFX mi3p5SmkvtDhYA7R3qLr0i/YHC4Y0saGtPKlnpncQnkzOU1u0xHv7Ar/uDpSS83V cNTCJt9IYUXG3FGegC0Z5Fw7LlE24xaouSZDfANtvFP/xfN2JHo3Xh2yAw+6M/i9 Ysm9c/0FSPDf7/+iqaObct6F9Pg4CvtDDviHvqU6yFxYGt3PiVBDIpzhIFTaqINJ cvsb0aiJDCCGIqOSZFePFlvTBP4AT0AKB4SwNw4Daw5cc/FjPdbx9iAkmLnKZTBh rs+d8guLmLyu24VaPgivzw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1769194101; x=1769280501; bh=h XPb+QrHCUgPPrXiacLZuddFplhPGYJSE5iT/NXvgHE=; b=w3Z7Wq85WBDq9hRcf O0kqwBr9gieMTc0HWCFOpaCQOYymACxAl2L+4ySUWe45ff0M9qXlvJ4cuto5hlnB OaGDKMW3z0Ji3DN8yKVmxpCVpoeqaa7gAaiZxRKm2oQkH0kqDVO0q78l64DRJnvr EYFHeNr2rhcjr1jrsF93eQqPO6hklQXyOqBiGIwu7eLhg70h8B/gdWVCxfs3SBkO maTvveXrL21/AXzVOiE/6RpJlr7jaeo3UgoengDUrt495GmsuJ1U9lyaoBdgkQwy tcykxHj9i6o1riu/kvWCJ+3txjahof+glzctyq5DMLQc5y/WANQf30cyjrtTPxd3 SJDAQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddugeelkedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertd dtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgr vhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepveelheefffehje ekudduvdfhgfffgeekieefieejveehjeeuueehudevgffgveefnecuffhomhgrihhnpehg lhhothdrihhonecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghp thhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepkhhktghhnhdrihhnse hgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlhesphhoshht ghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 23 Jan 2026 13:48:20 -0500 (EST) Message-ID: <00fe13de-cbfb-4652-8d62-7b7b15dddd39@aklaver.com> Date: Fri, 23 Jan 2026 10:48:17 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Resource Usage same In spite of fronting my DB server with Pgbouncer ? To: KK CHN , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/23/26 10:14 AM, KK CHN wrote: > > > > List, > I am fronting my postgres 16 server with  pgbouncer1.23.1 > > What surprises me,  even though I am deploying  pgbouncer as a separate > VM in front of DB server VM,  the top command shows the almost same > resource usage statistics in the case of load averages, Memory usage etc > on the DB Server,  whether I am infronting DB server with pgbouncer or not. > > Please find the top  output from the db server pasted here. > > https://glot.io/snippets/hf4ilogbz0 > > My Pgbouncer server  top output  shows littler resource usages in terms > of CPU, MEM usage > on the top out put of  pgbouncer VM ( load averagaes  less than 3 > always,  and Ram usage is very low,  swap usage almost nil.. > > > Why eventhough I have deployed  pgbouncer  for this setup why DB server > still shows large resource usage as in the pasted out put. That would seem logical to me as pgBouncer is just passing the connections to the Postgres server, the server is doing the heavy lifting of dealing with statements in the connections. From the top output it looks like you are working with some form of a EDB product. You need to specify what that product is and it's version. This list is for the community version of Postgres and people will assume that is what you are talking about. There are folks that maybe able to help with EDB versions, but they need to know what it is. > Regards, > Krishane