So interestingly, they are storing extra metadata in the object pointers, which means no more compressed oops (ie 32 bit pointers). Curious what the effect of that on heap sizes is considering most JVMs run with <32gb heaps
I think other people do this as well. As I recall, windows encodes r/w/execute memory permission into a mask at the top of the pointer so that they avoid a table look up when they take a fault.
I think if your heap is less than 32GB then this GC isn't for you in the first place - it's designed for really big heaps.
Is that true? Azul's similar GC was designed for large heaps, but it worked well with smaller heaps as well AFAIK.
The design documents say it's 'optimised for very large heaps'. 32GB isn't 'very large' these days.
It says: "Goals: Multi-terabyte heaps"
I don’t understand do you think that contradicts me?
I think ysleepy was agreeing with you and adding a data point to the discussion.