webrev: thread id in G1GCParPhaseTimesTracker
mikael.gerdin at oracle.com
Mon Mar 23 09:18:02 UTC 2015
On 2015-03-20 21:16, Eric Caspole wrote:
> Hi everybody,
> Yesterday I was chatting with Bengt about trying to encapsulate the GC
> worker thread id so it does not have to be explicitly passed in in so
> many GC methods just to record the timing stats. I made a first cut at
> this here:
Thread::current() is not a particularly cheap operation.
I think it's worth it to keep the worker_id to keep the overhead of
timing measurements to a minimum.
> More could be done here but I wanted to see if everyone thought it was
> worth continuing with it.
More information about the hotspot-gc-dev