> I recall that an object in Java takes somewhere between 16 and 24 bytes
> overhead, in addition to the data for the object itself, on a 32-bit
> java system, depending on the particular JVM (IBM vs. SUN, 1.4, 5, 6).

If you're worried about allocation time, you might want to look at this class 
that makes it easy to create object pools:

http://www.javolution.com/api/javolution/context/ObjectFactory.html

The Javolution project is concerned with the time-predictability of Java and 
produces high-quality, high-performance code.  The collection classes are 
especially useful.  I recommend it.


Greg Holmberg

Reply via email to