RFR (M): 8207266: ThreadMXBean::getThreadAllocatedBytes() can be quicker for self thread

[Hohensee, Paul]

Thanks for taking a look, Alan.

What does the “local management case” mean? I can certainly specify getCurrentThreadAllocatedBytes as being equivalent to getThreadAllocatedBytes(Thread.currentThread().getId().

Paul

From: Alan Bateman <Alan.Bateman at oracle.com>
Date: Wednesday, August 28, 2019 at 1:24 PM
To: "Hohensee, Paul" <hohensee at amazon.com>, OpenJDK Serviceability <serviceability-dev at openjdk.java.net>
Subject: Re: RFR (M): 8207266: ThreadMXBean::getThreadAllocatedBytes() can be quicker for self thread

On 28/08/2019 20:22, Hohensee, Paul wrote:

Please review a performance improvement for ThreadMXBean.getThreadAllocatedBytes and the addition of getCurrentThreadAllocatedBytes.

JBS issue: https://bugs.openjdk.java.net/browse/JDK-8207266
Webrev: http://cr.openjdk.java.net/~phh/8207266/webrev.00/
CSR: https://bugs.openjdk.java.net/browse/JDK-8230311

Previous email threads:
https://mail.openjdk.java.net/pipermail/serviceability-dev/2018-July/024441.html
https://mail.openjdk.java.net/pipermail/serviceability-dev/2018-August/024763.html

The CSR is for adding ThreadMXBean.getCurrentThreadAllocatedBytes. I’d be great for someone to review it.
I suspect the new method needs to be specified to be for the local management case only, and it might able to useful to specify it to be the equivalent of getThreadAllocatedBytes(Thread.currentThread().getId()).

-Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20190828/0f43bef9/attachment.html>