> > see it as performance optimisation. A GC impl which would have to deal > with fragmented, non continuous and resizing heap would have a hard > time to compete with the current VM.
Where's it written that the current VM has a continuous, non-fragmented static heap. This would only be possible if -Xms == -Xmx and I doubt this is handled as a special case. More modern garbage collectors (C4 & G1) deal with memory as pages or regions already and could (as C4 does) recycle unused pages back to the OS. I'm not intimately familiar with hotspot, but the bits of code I've read suggest it does all of it's allocation on a page by page basis, presumably to try and match the boundaries set out by the CPU/OS. Mike -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/znsYjV_D4gYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
