HeapRegionRemSetIterator question
John Cuthbertson
john.cuthbertson at oracle.com
Thu Apr 4 17:29:01 UTC 2013
Hi Everyone,
I've been looking at G1's HeapRegionRemSetIterator and I was wondering
if anyone knows why we pre-allocate instances of the iterator during
startup and then initalize them repeatedly when RSet scanning claims new
regions? I don't see much difference between this and stack allocating
new instances - other than saving the initialization of one or two
fields. Is there any reason not to stack allocate the iterator instances?
Thanks,
JohnC
More information about the hotspot-gc-dev
mailing list