Message-ID: <gh-pgjdbc-pgjdbc-3693-c3027555552@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 02 Jul 2025 11:42:14 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3693: Overhead of uncontended use of ResourceLock
In-Reply-To: <gh-pgjdbc-pgjdbc-3693@github.com>
References: <gh-pgjdbc-pgjdbc-3693@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3027555552
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3693
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3693#issuecomment-3027555552
Content-Type: text/plain; charset=utf-8

By the way,

>https://github.com/TechEmpower/FrameworkBenchmarks/wiki/Project-Information-Framework-Tests-Overview#general-test-requirements
> All test implementations **should be production-grade**. The particulars of this will vary by framework and platform, but the general sentiment is that the code and configuration should be suitable for a production deployment. The word should is used here because production-grade is our goal, but we don't want this to be a roadblock. If you're submitting a new test and uncertain whether your code is production-grade, submit it anyway and then solicit input from other subject-matter experts.

I'm not sure running with "deactivated locking" qualifies for "production-grade". It is like `-Xnoverify` to me. Sure it might speedup the startup in development, however, in production you'd better verify the bytecode :)