pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17467: Perf degradation after switching to latest jdbc drivers
4+ messages / 4 participants
[nested] [flat]
* BUG #17467: Perf degradation after switching to latest jdbc drivers
@ 2022-04-21 18:15 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 2 replies; 4+ messages in thread
From: PG Bug reporting form @ 2022-04-21 18:15 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: benleis1@gmail.com
The following bug has been logged on the website:
Bug reference: 17467
Logged by: Benjamin Leis
Email address: benleis1@gmail.com
PostgreSQL version: 13.4
Operating system: Linux
Description:
Due to the CVE-2022-21724 we upgraded our driver from 42.2.22 to 43.3.3.
We've now started to a large perf degradation during initial opens to the
database.
With a small perf test that just opens and tries a "select 1" we're getting
a ~2 - 2.5x slowdown on the connect times. Is this a known issue or
something that we can work around?
43.2.25 driver
INFO - New connection test
INFO - Open time: 25.00 Call time: 14.00
INFO - Open time: 24.00 Call time: 1.00
INFO - Open time: 19.00 Call time: 1.00
INFO - Open time: 16.00 Call time: 1.00
INFO - Open time: 26.00 Call time: 4.00
INFO - Open time: 20.00 Call time: 6.00
INFO - Open time: 20.00 Call time: 1.00
INFO - Open time: 16.00 Call time: 0.00
INFO - Open time: 19.00 Call time: 1.00
INFO - Open time: 19.00 Call time: 1.00
43.3.3 driver
INFO - New connection test
INFO - Open time: 57.00 Call time: 14.00
INFO - Open time: 58.00 Call time: 1.00
INFO - Open time: 62.00 Call time: 1.00
INFO - Open time: 54.00 Call time: 1.00
INFO - Open time: 59.00 Call time: 1.00
INFO - Open time: 56.00 Call time: 0.00
INFO - Open time: 59.00 Call time: 1.00
INFO - Open time: 61.00 Call time: 1.00
INFO - Open time: 57.00 Call time: 1.00
INFO - Open time: 58.00 Call time: 1.00
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #17467: Perf degradation after switching to latest jdbc drivers
@ 2022-04-25 13:36 Tom Lane <tgl@sss.pgh.pa.us>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 0 replies; 4+ messages in thread
From: Tom Lane @ 2022-04-25 13:36 UTC (permalink / raw)
To: benleis1@gmail.com; +Cc: pgsql-bugs@lists.postgresql.org
PG Bug reporting form <noreply@postgresql.org> writes:
> Due to the CVE-2022-21724 we upgraded our driver from 42.2.22 to 43.3.3.
> We've now started to a large perf degradation during initial opens to the
> database.
You'd be best off to inquire about that on the pgsql-jdbc mailing list.
This list deals with issues in the core server, which I doubt that is.
FWIW, you might want to double-check that you've not accidentally
changed any connection parameters. It could be useful to enable
log_connections on the server, so you can see if the connection
attempts look any different in the server log.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Fwd: BUG #17467: Perf degradation after switching to latest jdbc drivers
@ 2022-04-25 16:58 Benjamin Leis <benleis1@gmail.com>
parent: PG Bug reporting form <noreply@postgresql.org>
1 sibling, 1 reply; 4+ messages in thread
From: Benjamin Leis @ 2022-04-25 16:58 UTC (permalink / raw)
To: pgsql-jdbc@postgresql.org
Forwarding this to the jdbc list.
Bug reference: 17467
Logged by: Benjamin Leis
Email address: benleis1@gmail.com
PostgreSQL version: 13.4
Operating system: Linux
Description:
Due to the CVE-2022-21724 we upgraded our driver from 42.2.22 to 43.3.3.
We've now started to see a large perf degradation during initial opens to
the
database.
With a small perf test that just opens and tries a "select 1" we're getting
a ~2 - 2.5x slowdown on the connect times. Is this a known issue or
something that we can work around?
43.2.25 driver
INFO - New connection test
INFO - Open time: 25.00 Call time: 14.00
INFO - Open time: 24.00 Call time: 1.00
INFO - Open time: 19.00 Call time: 1.00
INFO - Open time: 16.00 Call time: 1.00
INFO - Open time: 26.00 Call time: 4.00
INFO - Open time: 20.00 Call time: 6.00
INFO - Open time: 20.00 Call time: 1.00
INFO - Open time: 16.00 Call time: 0.00
INFO - Open time: 19.00 Call time: 1.00
INFO - Open time: 19.00 Call time: 1.00
43.3.3 driver
INFO - New connection test
INFO - Open time: 57.00 Call time: 14.00
INFO - Open time: 58.00 Call time: 1.00
INFO - Open time: 62.00 Call time: 1.00
INFO - Open time: 54.00 Call time: 1.00
INFO - Open time: 59.00 Call time: 1.00
INFO - Open time: 56.00 Call time: 0.00
INFO - Open time: 59.00 Call time: 1.00
INFO - Open time: 61.00 Call time: 1.00
INFO - Open time: 57.00 Call time: 1.00
INFO - Open time: 58.00 Call time: 1.00
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #17467: Perf degradation after switching to latest jdbc drivers
@ 2022-04-27 14:47 Dave Cramer <davecramer@postgres.rocks>
parent: Benjamin Leis <benleis1@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dave Cramer @ 2022-04-27 14:47 UTC (permalink / raw)
To: Benjamin Leis <benleis1@gmail.com>; +Cc: List <pgsql-jdbc@postgresql.org>
FWIW,
I released 42.2.25 to address this issue as well. PostgreSQL JDBC Changelog
<https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.25;
<https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.25>However
it would be nice to see your test code so that I can verify.
Regards,
Dave Cramer
www.postgres.rocks
On Mon, 25 Apr 2022 at 12:58, Benjamin Leis <benleis1@gmail.com> wrote:
>
> Forwarding this to the jdbc list.
>
> Bug reference: 17467
> Logged by: Benjamin Leis
> Email address: benleis1@gmail.com
> PostgreSQL version: 13.4
> Operating system: Linux
> Description:
>
> Due to the CVE-2022-21724 we upgraded our driver from 42.2.22 to 43.3.3.
> We've now started to see a large perf degradation during initial opens to
> the
> database.
>
> With a small perf test that just opens and tries a "select 1" we're
> getting
> a ~2 - 2.5x slowdown on the connect times. Is this a known issue or
> something that we can work around?
>
> 43.2.25 driver
> INFO - New connection test
> INFO - Open time: 25.00 Call time: 14.00
> INFO - Open time: 24.00 Call time: 1.00
> INFO - Open time: 19.00 Call time: 1.00
> INFO - Open time: 16.00 Call time: 1.00
> INFO - Open time: 26.00 Call time: 4.00
> INFO - Open time: 20.00 Call time: 6.00
> INFO - Open time: 20.00 Call time: 1.00
> INFO - Open time: 16.00 Call time: 0.00
> INFO - Open time: 19.00 Call time: 1.00
> INFO - Open time: 19.00 Call time: 1.00
>
> 43.3.3 driver
> INFO - New connection test
> INFO - Open time: 57.00 Call time: 14.00
> INFO - Open time: 58.00 Call time: 1.00
> INFO - Open time: 62.00 Call time: 1.00
> INFO - Open time: 54.00 Call time: 1.00
> INFO - Open time: 59.00 Call time: 1.00
> INFO - Open time: 56.00 Call time: 0.00
> INFO - Open time: 59.00 Call time: 1.00
> INFO - Open time: 61.00 Call time: 1.00
> INFO - Open time: 57.00 Call time: 1.00
> INFO - Open time: 58.00 Call time: 1.00
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2022-04-27 14:47 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-04-21 18:15 BUG #17467: Perf degradation after switching to latest jdbc drivers PG Bug reporting form <noreply@postgresql.org>
2022-04-25 13:36 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-04-25 16:58 ` Benjamin Leis <benleis1@gmail.com>
2022-04-27 14:47 ` Dave Cramer <davecramer@postgres.rocks>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox