Next: ObjectMemory-builtins, Previous: ObjectMemory class-saving the image, Up: ObjectMemory [Index]
Answer the number of times that the old-space allocator found no block that was at least as big as requested, and had to ask the operating system for more memory.
Answer the number of times that the old-space allocator found a block that was exactly as big as requested.
Answer the number of free blocks that the old-space allocator had to examine so far to allocate all the objects that are in old-space
Answer the number of times that the old-space allocator could not find a block that was exactly as big as requested, and had to split a larger free block in two parts.
Answer the number of bytes that is taken by an ordinary object pointer (in practice, a field such as a named instance variable).
Answer the number of bytes that is taken by an object table entry (in practice, the overhead incurred by every object in the system, with the sole exception of SmallIntegers).
Answer the number of bytes in the ‘eden’ area of the young generation (in practice, the number of allocated bytes between two scavenges).
Answer the number of bytes that are currently filled in the ‘eden’ area of the young generation.
Answer the number of bytes in the special heap devoted to objects that the garbage collector cannot move around in memory.
Answer the number of bytes that are currently filled in the special heap devoted to objects that the garbage collector cannot move around in memory.
Answer the number of oldspace compactions that happened since the VM was started.
Answer the number of objects that the garbage collector cannot move around in memory.
Answer the number of entries that are currently free in the object table.
Answer the number of global garbage collections (collection of the entire heap) that happened since the VM was started.
Answer the number of times that oldspace was grown since the VM was started.
Answer the number of entries that are currently allocated for the object table.
Answer the number of objects that reside in the old generation.
Answer the number of scavenges (fast collections of the young generation) that happened since the VM was started.
Answer the number of weak objects that the garbage collector is currently tracking.
Answer the number of bytes in the old generation.
Answer the number of bytes that are currently filled in the old generation.
Answer the average number of bytes that are found to be garbage during a global garbage collections.
Answer the average number of bytes that are found to be garbage during a scavenge.
Answer the average percentage of allocated bytes that are found to be garbage during a scavenge. If this number falls below 60-70 you should definitely increment the size of the eden, because you risk that scavenging is eating a considerable fraction of your execution time; do the measurement on a restarted image, so that the extra tenuring incurred when creating long-lived objects such as classes or methods is not considered.
Answer the number of bytes in the ‘survivor’ area of the young generation (the area to which young objects are relocated during scavenges).
Answer the number of bytes that are currently filled in the ‘survivor’ area of the young generation.
Answer the average number of bytes that are promoted to oldspace during a scavenge.
Answer the average number of milliseconds between two global garbage collections.
Answer the average number of milliseconds between decisions to grow the heap.
Answer the average number of milliseconds between two scavenges (fast collections of the young generation).
Answer the average number of milliseconds that a global garbage collection takes.
Answer the average number of milliseconds that compacting the heap takes. This the same time that is taken by growing the heap.
Answer the average number of milliseconds that a scavenge takes (fast collections of the young generation).
Next: ObjectMemory-builtins, Previous: ObjectMemory class-saving the image, Up: ObjectMemory [Index]