MIME-Version: 1.0
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Tue, 30 Apr 2024 21:21:14 -0400
Message-ID: <CANzqJaBybDrzRfjseKPS+3EhBFrLuU_kfSFME_2+VSoR-DLOdw@mail.gmail.com>
Subject: Posgresql 14 and CarbonBlack on RHEL8?
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000234e8706175a4efe"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBybDrzRfjseKPS%2B3EhBFrLuU_kfSFME_2%2BVSoR-DLOdw%40mail.gmail.com>
Precedence: bulk

--000000000000234e8706175a4efe
Content-Type: text/plain; charset="UTF-8"

(CarbonBlack is cross-platform AV software sold by VMware.)

Currently we're running PG 9.6.24 on RHEL 6.10 with CB (version unknown to
me) in production, and testing PG 14.11 on RHEL 8.9 with CB 2.15.2
(hopefully going into production next month).

Both old and new VMs are 32 CPU with 128GB RAM.
Nothing but PG, CB and itsm software runs on these systems.

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).

The small RHEL8/PG14 non-prod systems show similar load when lots of SELECT
statements run.

Has anyone else seen this?  If so, how did you resolve it?

--000000000000234e8706175a4efe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>(CarbonBlack is cross-platform AV software sold by VM=
ware.)</div><div><br></div>Currently we&#39;re running PG 9.6.24 on RHEL 6.=
10 with CB (version unknown to me) in production, and testing PG 14.11 on R=
HEL 8.9 with CB 2.15.2 (hopefully going into production next month).<div><b=
r></div><div>Both old and new VMs are 32 CPU with 128GB RAM.</div><div>Noth=
ing but PG, CB and itsm software runs on these systems.</div><div><br></div=
><div>When running stress tests on the systems (in prod, during the mainten=
ance 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.</div><div>The RHEL6 system doesn&#39;t bat an eye at running =
the exact same test (36 cron jobs running psql executing=C2=A0SELECT statem=
ents).</div><div><br></div><div>The small RHEL8/PG14 non-prod systems show =
similar load when lots of SELECT statements=C2=A0run.</div><div><br></div><=
div>Has anyone else seen this?=C2=A0 If so, how did you resolve it?</div><d=
iv><br></div></div>

--000000000000234e8706175a4efe--