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 1s1zNz-00GYg6-9G for pgsql-general@arkaria.postgresql.org; Wed, 01 May 2024 02:07:55 +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 1s1zNw-00A3ca-LS for pgsql-general@arkaria.postgresql.org; Wed, 01 May 2024 02:07:53 +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 1s1zNw-00A3cS-B0 for pgsql-general@lists.postgresql.org; Wed, 01 May 2024 02:07:53 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1zNq-000rSb-Eu for pgsql-general@postgresql.org; Wed, 01 May 2024 02:07:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 44127ivb1854444; Tue, 30 Apr 2024 22:07:44 -0400 From: Tom Lane To: Ron Johnson cc: pgsql-general Subject: Re: Posgresql 14 and CarbonBlack on RHEL8? In-reply-to: References: Comments: In-reply-to Ron Johnson message dated "Tue, 30 Apr 2024 21:21:14 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1854442.1714529264.1@sss.pgh.pa.us> Date: Tue, 30 Apr 2024 22:07:44 -0400 Message-ID: <1854443.1714529264@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Ron Johnson writes: > When running stress tests on the systems (in prod, during the maintenance > window), 171K events/second are generated on the RHEL8 servers, and CB > needs (according to top(1)) 325% of CPU to handle that, and still dropping > 92% of them. > The RHEL6 system doesn't bat an eye at running the exact same test (36 cron > jobs running psql executing SELECT statements). Is JIT enabled on the newer system? If so try turning it off, or else raise the associated cost settings. We've seen lots of reports of workloads where, by default, the planner is too aggressive about applying JIT. regards, tom lane