Обсуждение: BUG #17467: Perf degradation after switching to latest jdbc drivers

Поиск
Список
Период
Сортировка

BUG #17467: Perf degradation after switching to latest jdbc drivers

От
PG Bug reporting form
Дата:
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

Re: BUG #17467: Perf degradation after switching to latest jdbc drivers

От
Tom Lane
Дата:
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