Do objects with a lot of reference fields (except arrays) devastate Hotspot JVM's GC(s) heap traversal performance? : <p>Imagine that I define <a href="https://github.com/OpenHFT/SmoothieMap/blob/80a6a2f9dcba246cdf6c6c01259c7fca90a2fd68/src/main/java/net/openhft/smoothie/Segment.java#L860-L867" rel="noreferrer">a class with dozens of reference fields</a> (instead of using reference arrays such as <code>Object[]</code>), and instantiate this class pretty heavily in an application.</p>

<p>Is it going to affect the performance of garbage collector in Hotspot JVM, when it traverses the heap to calculate reachable objects? Or, maybe, it would lead to significant extra memory consumption, for some JVM's internal data structures or class metadata? Or, is it going to affect the efficiency of an application in some other way?</p>

<p>Are those aspects specific to each garbage collector algorithm in Hotspot, or those parts of Hotspot's mechanics are shared and used by all garbage collectors alike?</p>
