Re: Class with only methods - less memory?
Daniel Dyer wrote:
If there are no fields whatsoever, then there is nothing to be gained by
having more than one instance of the class (unless its methods are not
re-entrant and you need concurrent invocations, in which case you could
consider pooling multiple instances). If you do put your data on disk,
This is an interesting idea. Does making a copy of a class with
non-reentrant methods make the class thread safe? I'm guessing no way.
I think the original poster was asking if the method byte-code (is that
the correct term?) is copied when the class (any class) was instanced,
or if just the local variables are copied. I'd assume he's correct and
only variables are copied, but I don't know. I'd assume that the
reference created for a "method only" object is just 8 bytes in most
implementations, or a bit more.
I think you should investigate some ways of managing memory, rather than
try to count bytes for JVM internal structures. Weak references might
help out (WeakReference). Soft references might be useful as well
(SoftReference). Both are derived from java.lang.ref.Reference.
java.lang.ref also includes a ReferenceQueue object to help you manage
your references.