Method Bloat

[Nathan Reynolds]

I have been discussing an idea with Guy Korland via email. I thought
I should post this idea here so that the wider community can comment.

If I understand Deuce STM, it makes a duplicate copy of every method
of every class loaded. This adds a significant overhead of memory.
If the JVM allowed for adding methods after loading a class, then it
would be easy to simply add the required methods for each
transaction. Alas, it doesn't.

So, instead, why not create skeleton copies of every method. These
skeleton copies are either empty if the method returns void or has
return 0 or null if the method returns a value. When the method is
needed by a transaction, then redefine the used classes and fill in
the contents of the required methods. Thus, the skeletons methods are
all there but don't get any meat until needed. This will greatly save
on memory and reduce class loading overhead.

[Guy Korland]

This method can work and save some memory, but I don't think it's a real problem...

Do you have such use case where the code memory consumption is an issue?

Regards,
Guy Korland

--
You received this message because you are subscribed to the Google Groups "Deuce-STM" group.
To post to this group, send email to deuc...@googlegroups.com.
To unsubscribe from this group, send email to deuce-stm+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/deuce-stm?hl=en.