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 1s25at-00HLCu-UN for pgsql-general@arkaria.postgresql.org; Wed, 01 May 2024 08:45:39 +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 1s25Zs-00BsBZ-3m for pgsql-general@arkaria.postgresql.org; Wed, 01 May 2024 08:44:37 +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.94.2) (envelope-from ) id 1s25Zr-00BsBR-Mr for pgsql-general@lists.postgresql.org; Wed, 01 May 2024 08:44:36 +0000 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s25Zl-000z1P-P6 for pgsql-general@postgresql.org; Wed, 01 May 2024 08:44:35 +0000 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-23319017c4cso4230769fac.2 for ; Wed, 01 May 2024 01:44:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714553067; x=1715157867; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=n67HjTnmpYeXUNo3JYqYVSyPz0wiSlXGkWTauK+dMUA=; b=JJuEep381hc6GrpxZk3Rzo2JHke099m7xrd+FNPF1kX5ZAGzKkATHpXQH1yttTCxT2 lMze7GTmvvJZA8Nrxgo+QI8r0aWEGwc8PGN7z21VFK6Ht4eLkOAUuoWgDDHrsTLRNX+p CN5Rgf/wqSG32MIH9vtrKry5xN33HR7BMF5Xc8eYqMgFXfhJLxSI1tPSnHutXKkO3Bz2 sTu4YlE+em/ixOZdgNYIr/NTksfS1AOkiDTF8XBPR6tmj7xIsQdj/AkmqN93ToxVrn0V y3PGN+dkJAoGV7rA2Ej/i1ufs556A1ZwSL0xF27nN4of30aOk1yE0AM0g1srv1FZZqHG Ccuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714553067; x=1715157867; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=n67HjTnmpYeXUNo3JYqYVSyPz0wiSlXGkWTauK+dMUA=; b=UVLwXn0G/eoKHJzCYaAr5TlCOaXo8mjTVB+ITyG2eyoxClseP8XMiOwmevl5jeTZ7K tB4cqT0wM9uUUPghrTfxUe/R7Smx3/S6jxKEVHSOw8m8fuPYSf7VT0LslRL3C5Z4H4qo AI+W9rneK3A6UrfWO1R5EtWt9x2wHF3lsYDpkT4IMLGntTs2Yc2gOPfoLn0sitE1i7Fk XwCPIcgCmuk68XOpYmQrKngdUSwH9bGIsCf1iZxS02bWO9yOsre4opCEKitFpGzzUmkW FGaZjps/gNpFAB0OGFrCW8F0DGc0m6XvDTcOA6MScGTQKuJfAe2Hz8uYSFDWMenjkO34 YvTA== X-Gm-Message-State: AOJu0YybtQwIEAig/aGf24uCoUgFjgGoJ16Bcol3CNbfIeHhPaZvuZL5 NTF9IC2bzwTxfYMg70EJsTgKl7JAHszCnh0LuccbC79jZFR5ej7tAk+HDgBfjDAuJ79Sv16YKku I/eaSbmm/hetHgmHlqNo6LpbDXxQOzQ== X-Google-Smtp-Source: AGHT+IHchnkhqLiDF2i5gAIzpfihvhUcwnXPwrJnwTAJAkzCA97Bo80QGDipGZf4ztaNTEk+Lgz/JcGRCOE9Yzo5nT8= X-Received: by 2002:a05:6870:f28b:b0:229:faa9:3b35 with SMTP id u11-20020a056870f28b00b00229faa93b35mr1587738oap.21.1714553067188; Wed, 01 May 2024 01:44:27 -0700 (PDT) MIME-Version: 1.0 References: <1854443.1714529264@sss.pgh.pa.us> In-Reply-To: <1854443.1714529264@sss.pgh.pa.us> From: Ron Johnson Date: Wed, 1 May 2024 04:44:16 -0400 Message-ID: Subject: Re: Posgresql 14 and CarbonBlack on RHEL8? To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000084b9b50617607e50" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000084b9b50617607e50 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 30, 2024 at 10:07=E2=80=AFPM Tom Lane wrote= : > Ron Johnson writes: > > When running stress tests on the systems (in prod, during the maintenan= ce > > 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. > A puzzling suggestion. Why should it impact AV software? At one point, I disabled JIT to test its impact on PG, performance was a bit of a wash (some queries were a bit faster, some were a bit slower), but I didn't monitor CB. Just now, I did ALTER SYSTEM SET jit=3D'off'; and re-ran the stress test. = No impact to CarbonBlack. --00000000000084b9b50617607e50 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Apr 30, 2024 at 10:07=E2=80=AFPM = Tom Lane <tgl@sss.pgh.pa.us>= wrote:
Ron Johnson <ronljohnsonjr@gmail.com> writes:
> When running stress tests on the systems (in prod, during the maintena= nce
> 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 drop= ping
> 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?=C2=A0 If so try turning it off, or else=
raise the associated cost settings.=C2=A0 We've seen lots of reports of=
workloads where, by default, the planner is too aggressive about
applying JIT.

A puzzling=C2=A0suggestio= n.=C2=A0 Why should it impact AV software?

At one = point, I disabled JIT to test its impact on PG, performance was a bit of a = wash (some queries were a bit faster, some were a bit slower), but I didn&#= 39;t monitor CB.

Just now, I did ALTER SYSTEM SET = jit=3D'off'; and re-ran the stress test.=C2=A0 No impact to CarbonB= lack.

--00000000000084b9b50617607e50--