Feb. 13, 2012
2:02 p.m.
On Feb 13, 2012, at 2:47 PM, Guido Stepken wrote:
I did analyse some of these "memory pumping effects" in Pharo. Come from overuse of "inheritance", that causes big objects with hundreds of methods to be created and garbaged, just for short tasks.
The number of methods do not influence *at all* the size on an object. Methods are on the class, the object point to its class, no need to allocate *any* memory. The only thing that costs memory is *state*. Marcus -- Marcus Denker -- http://marcusdenker.de