hsperfdata causing long GC/safepoint times: Don't use mmap?

Dean Long dean.long at oracle.com
Thu Mar 26 20:15:09 UTC 2015

I'm curious, does the problem go away if the mmap doesn't use MAP_SHARED?


On 3/26/2015 8:14 AM, Evan Jones wrote:
> At Twitter, I recently discovered that the hsperfdata file that is created
> by default by the JVM causes long safepoint and GC pauses. It turns out
> that writes to mmap-ed files can block until disk I/O completes, even if
> the I/O is to another disk. For details see:
> http://www.evanjones.ca/jvm-mmap-pause.html
> We have been experimenting with adding the -XX:+PerfDisableSharedMem JVM
> flag on a number of our latency sensitive services, and have seen a
> significant improvement. Our JVM team (which I am *not* part of), is
> investigating potential changes to the JVM to prevent this.
> Any suggestions for an approach to solving this problem that could be
> accepted into Hotspot itself? Some options:
> * Make the location of this file configurable (this was set with
> java.io.tmpdir for a time, but then was reverted; see
> http://bugs.java.com/view_bug.do?bug_id=6447182)
> * Use shared memory that is not backed by a file?
> * Something else I'm not considering?
> Thanks!
> Evan Jones

More information about the hotspot-runtime-dev mailing list