The memory consumption of JNode must be br

Hi,
and shrink the compiled classes with some Obfuscation/Optimizer Tool ?

This could help to reduce the memory usage ... depending on the grade of the optimization choosen.

But we could have problems then to read error messages related to methods and variables in that classes.

Bye,
Sandro

Onheap shows lots of iterators created during boot.

Replace
for(Object obj : list) {...}
with
for(int i=0; i<list.size(); i++) {obj = list.get(i); ...}
in often-used loops to reduce the number of temporary Iterator objects created.

I know this saves a bit of memory, but a good GC should solve this easily (and i'm working on this good gc).
So please don't make the code more complex & less efficient by a minor (and only temporary) optimization.

Ewout

The internal structures of the VM have been optimized for size. This saves about 2mb in the bootimage.

Now the best way to reduce the bootimage size is to reduce the number of classes in the bootimage.

No specific tasks are left on this subject.

However it will remain a constant point of attention.