pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: Sanne (@Sanne) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3693: Overhead of uncontended use of ResourceLock
Date: Tue, 01 Jul 2025 15:28:30 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
I have now results from a benchmark run in which the locks are being bypassed, and it looks very promising:
The experimental patch I've been running is this one:
- https://github.com/pgjdbc/pgjdbc/commit/da092f524abd228b4d2f77e45fab6cbe40f0fbb7
In the graph, the same code is being run on both the blue and green bars. The difference is the JVM property being activated on the left one.
The two bars on the right represent the "512" scenario, in which we have highest CPU demand; obviously that's were this is most effective.
And let me add: the patch draft is not comprehensive. It's bypassing some of the locks as a POC, but I still see some of them, so I could improve further.
view thread (14+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #3693: Overhead of uncontended use of ResourceLock
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox