On Tue, 24 Mar 2026 05:47:04 GMT, David Holmes <[email protected]> wrote:

> I'd like to know more about the way this API was being (mis)used to get a 
> better sense of whether this is just pandering to an extreme case. I'm not a 
> fan of all this "micro-optimisation" and it seems to me this should be 
> slowing down normal usecases. I would like to see performance numbers for all 
> platforms (Linux, macOS, Windows).
> 
> The synchronization is needed.

I am trying to get more details on the usage and problems arount 
Thread.setName(). What I do remember was:
1. It was Cassandra
2. Yes, they added some transient context in the thread name
3. The impact was considerable

However, ~600ns seems like it should perhaps not show up much, even when 
getting called gazillions of times. I'm checking if maybe we are looking at a 
heavily contented case, or if there is something else going on.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/30374#issuecomment-4117465630

Reply via email to