Ok. Then it must have been the ghost, that causes heavy "memory pumping", even under zero load, see CPU monitor.
Its quite difficult not to say *impossible* to run Pharo even for simple tasks within a small vserver account with 256 or 512 MB reserved or dynamically assigned memory space.
But i agree, that Smalltalk *can* be designed to run well within 1MB of RAM :-)
have fun, Guido Stepken
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