linux os processor optimizations for OpenJDK GC performance enhancement

Ram Krishnan ramkri123 at gmail.com
Fri Apr 14 04:36:27 UTC 2017


Thanks Andrew.

​>>Surely there is: a thread could have its TLAB allocated from a region
>>local to that socket (or core), and the GC thread for that region
>>could run on the same socket.  It only works for young gen, but that's
>>a lot of the problem.

A clarification -- does the TLAB allocation apply to tenured space also? If
not, the above would work only for young gen cases where there is no
promotion to tenured right?

Thanks,
Ramki

On Thu, Apr 13, 2017 at 12:55 PM, Ram Krishnan <ramkri123 at gmail.com> wrote:

>
> ---------- Forwarded message ----------
> From:
> ​​
> Andrew Haley <aph at redhat.com>
> Date: Thu, Apr 13, 2017 at 9:52 AM
> Subject: Re: linux os processor optimizations for OpenJDK GC performance
> enhancement
> To:
> ​​
> hotspot-gc-dev at openjdk.java.net
>
>
> On 13/04/17 16:33, Kim Barrett wrote:
> > An application thread may touch memory in any region; there is no
> > notion of a thread being "scoped" to a specific set of regions. While
> > it might happen that a thread would only touch regions not being
> > worked on by the collector, there is no a priori way to know that.
>
> ​​
> Surely there is: a thread could have its TLAB allocated from a region
> local to that socket (or core), and the GC thread for that region
> could run on the same socket.  It only works for young gen, but that's
> a lot of the problem.
>
> Andrew.
>
>
>
>
> --
> Thanks,
> Ramki
>



-- 
Thanks,
Ramki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20170413/31585b6f/attachment.html>


More information about the hotspot-gc-dev mailing list