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.94.2) (envelope-from ) id 1tfMVN-001nkx-0J for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 17:14:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfMVM-00659L-3G for pgsql-general@arkaria.postgresql.org; Tue, 04 Feb 2025 17:14:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfMVK-00659D-Qf for pgsql-general@lists.postgresql.org; Tue, 04 Feb 2025 17:14:31 +0000 Received: from fhigh-a2-smtp.messagingengine.com ([103.168.172.153]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tfMVI-0039vF-0T for pgsql-general@postgresql.org; Tue, 04 Feb 2025 17:14:29 +0000 Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id 79951114013D; Tue, 4 Feb 2025 12:14:27 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Tue, 04 Feb 2025 12:14:27 -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=fm2; t=1738689267; x=1738775667; bh=Sw1U0fIDtSSyA9pxn+WY/YNxHkGjzgUQKHnFZByRB30=; b= HHZQKBWxEu3EM8GltP2IZYQ0UQPTQhZQpyHiHGgs/0duFqsgaz+FD5PlF8XQffjD 9R1QhPDTU3OXOWKAsyYgkdWOud7qUQW8TdAiBzTGyKErmMZ9RHSBmgAgsX2S/++N eqAjOaZLaRcGp4O1akC3b2MDH5U1fXQq6NsnEPz9yFcJ6oBnqeUGQtHMcQr7WhV/ FbU2tZKgOad2PfonpVavZydXNG7CgZHInOWIZKmkPL9hic3oIYwaua7sjIPDN6/w CNxYg+ednAP+I68TTxMCuEv4ld/7teTKD2KQwh0sI91LbRufs9tRXHwPlFobyiSp vVAvPRthiMGs1WpX6sHTrw== 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=fm3; t=1738689267; x=1738775667; bh=S w1U0fIDtSSyA9pxn+WY/YNxHkGjzgUQKHnFZByRB30=; b=kxVozjOpkv2ZI9sJn Gj0+vuqD1MY3An7JzEb4CwkPE/hv0g0YQd2JBbfdIB258nxpcg9Ph6+VhyEx7A4o njNReK/1YJz4od+/nxTDq3DGzxcguwihkU+bptf8KmK5WOcc3DYpTA7jj8SMxFUW g9eRi4NffAqO6WQX0m+OXTvRsbO9RO4YGgQwJIsNM3AJueU/q68f8eR3PpiKNwRH AdvtkxU/Xivcy3c56vY+6EIX/NnnQ/Mk38yQdtiC91/AMFflz5RtcZpMdAH0Kaav GjzHIXjfDzUjpa23tBN5FWeY5n2q+TCohUBrZFRSgP1tDBXqJ52VND7r8aiM+P/p Ju2TA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvuddutdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgg gfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgv rhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrg htthgvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeejffekjeeujeehgeeh geektdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgv rhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtph houhhtpdhrtghpthhtohepkhhktghhnhdrihhnsehgmhgrihhlrdgtohhmpdhrtghpthht ohepphhgshhqlhdqghgvnhgvrhgrlhesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 4 Feb 2025 12:14:26 -0500 (EST) Message-ID: Date: Tue, 4 Feb 2025 09:14:26 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Postgres performance issue with High CPU usage 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 2/4/25 09:11, KK CHN wrote: > List, > > Could someone point out how can I trace what causes the edb-postgres > process with  %CPU usage reaching 73 to 80.1 percentage  in this box. >  What's wrong with the server VM.. What version of EDB database are you using? If it is not their install of the community version available here: https://www.postgresql.org/download/windows/ then this is probably a question for their tech support. > > The clients connecting the databases experience  slow responses .. > > The top out put of the DB server is  pasted below.. > > > Any hints  much appreciated to trouble shoot this unusual load on the > server instance. > > Thank you, > Krishane. > > > > > I > > top - 22:34:13 up 61 days,  7:43,  3 users,  load average: 8.76, 9.92, 19.12 > Tasks: 697 total,   9 running, 687 sleeping,   1 stopped,   0 zombie > %Cpu(s): 34.3 us, 18.7 sy,  0.0 ni, 46.2 id,  0.0 wa,  0.5 hi,  0.3 si, >  0.0 st > MiB Mem :  31837.6 total,   1296.9 free,  11447.0 used,  27969.1 buff/cache > MiB Swap:   8060.0 total,   7400.0 free,    660.0 used.  20390.5 avail Mem > >     PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ > COMMAND > 4007576 enterpr+  20   0 8944520 951764 941212 R  80.1   2.9   0:57.24 > edb-postgres > 4035945 enterpr+  20   0 8943056 472108 463068 R  79.7   1.4   0:11.48 > edb-postgres > 4020721 enterpr+  20   0 8925752 702836 689644 S  73.1   2.2   0:27.99 > edb-postgres > 4036409 enterpr+  20   0 8916540 368084 363772 S  43.5   1.1   0:01.31 > edb-postgres > 4036410 enterpr+  20   0 8928512 481808 469852 S  32.2   1.5   0:03.52 > edb-postgres >  442070 enterpr+  20   0 8908184 181248 180096 S  13.0   0.6   1391:16 > edb-postgres > 4041239 enterpr+  20   0 8921696 995.0m 986.1m S   9.0   3.1   0:00.75 > edb-postgres > 4041225 enterpr+  20   0 8921856 -- Adrian Klaver adrian.klaver@aklaver.com