g1: remembered set scan costs very high w/ LRU cache type of behavior
peter.schuller at infidyne.com
Sat Feb 27 15:18:31 PST 2010
> The problem you're seeing may be addressed by some
> work in progress that is being done under CR
> 6923991: G1: improve scalability of RSet scanning
> I don't think that work has been released yet.
Well, if this commit constitutes the work:
Then I suspect I have it, because the JDK comes from:
Which is 7 days after the commit happened.
I'll see about building from source to maks sure.
However, reading about it my initial impression that it is probably
not the same issue as it seems to be about many-core scalability of
the RS scanning. In my case I see poor performance even with a single
core, and to the extent it is a scaling issue I get the impression it
is a function of the number of RS tracked writes rather than the
number of CPU cores.
> If it hasn't,
> with your permission, we'll try your test program with
> it and see how well it does.
Btw, I discovered something else. I have previously been doing some
testing on JDK:s build from the jdk 1.7 bsdport on FreeBSD and had
stability issues where the JVM would suddenly exit with no message
when I ran my clojure persistent LRU test with G1. I just hit this
behavior on the Linux host earlier today, with the snapshot binary
mentioned above, which means I can no longer chalk it up to a FreeBSD
I doubt I can do much to narrow it down to a very small test case, but
I could tidy up the test case a bit and make that available, and
perhaps produce an executable .jar with clojure + the test case if
that helps. I suspect (based on speculation rather than evidence) that
the allocation and write patterns being generated by the use of
persistent/immutable data structures is key to triggering it.
That is, unless there is an actual System.exit() somewhere in the
codebase... but I highly doubt there would be code that does this as a
function of some behavior which depends on the garbage collector
/ Peter Schuller
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
More information about the hotspot-gc-dev