For each benchmark, I plot

  1. s/c: graphs comparing the site rental and volumes, cumulatively, of the top 32 sites and partitions, ordered by site rental.
  2. 3D plots of (time of death, lifetime, volume) of the immortal partition and the other top 15 partitions. The yellow "shadows" point back to the time at which the objects were allocated. The boxes are an attempt to group objects that die together.

Commentary

benchmark s/csr at 95+%vol at 95+%
compress 3 4 4 10
jess 1-5 3 5 14
raytrace 3-5 2 4 10
db 2-3 4 4 9
javac 2-9 2 4 6
jack 2-4 4 4 12
antlr 2-8 3 4 5
bloat* 3-17 3 5 7
fop 3-4 4 5 22
hsqldb 6-8 2 4 9
jython 2-8 2 5 10
pmd 2-8 2 5 5
ps 5-12 3 5 8
  1. Consistently few partitions and few sites capture most SR.
  2. Number of partitions to capture most volume seems bi-modal (except for fop).
  3. More partitions (i.e. more variability) than for java+compiler_scope.
benchmarkclusters (0=immortal)

Here's how to read our 3D plots. Time of death is plotted horizontally (from right 0% to left 100%). Age is plotted from back o% to front 100%. Volume that died is plotted vertically. Note that it is impossible for any point to fall SE of the green line (its age would be greater than its time of death). The plots have been annotated with coloured rectangles that group objects that seem to live and die together, i.e. with opposing corners at (phase_end-max_age,min_age) and (phase_end,max_age).