Do objects ever get allocated directly into the old generation?
In 1.4.1 there two situations where allocation may occur directly into the old generation. • If an allocation fails in the young generation and the object is a large array that does not contain any references to objects, it can be allocated directly into the old generation. In some select instances, this strategy was intended to avoid a collection of the young generation by allocating from the old generation. The threshold size for 1) is 64k words. The default size for PretenureSizeThreshold is 0 which says that any size can be allocated in the young generation. In 1.4.2 case 1) the 64k word threshold continues to be true for the incremental collector (-Xincgc). For the default collector and the concurrent collector (-XX:+UseConcMarkSweepGC) the threshold value has been changed so that an attempt to allocate into the old generation only occurs if the size of the allocation is larger than the entire young generation (available space when it is empty). It was observed that there were cas
Related Questions
- For objects moving away but not directly away in our light of sight, could we take measurements from different parts of the Earth and compare the readings to figure out precise velocity?
- Can I pass Externalizable objects by value using RMI, or do the objects have to implement Serializable directly?
- Do objects ever get allocated directly into the old generation?
