On Nov 7, 2009, at 8:30 PM, Martin McClure wrote:
Adrian Lienhard wrote:
Yes, in "normal" use of Pharo, holding the sources in memory would only consume a fraction of the available RAM. Some applications, however, have several hundred images running at the same time on a server. In this case the picture looks very different again.
It would be easy to strip all sources from production images, but the simple way of doing that would mean any debugging would be done on decompiled code.
I think Marcus' idea of swapping in/out ressources is very interesting. We could get rid of the ancient sources handling but still have a low, or even lower, memory footprint.
This would be even better. ImageSegments are a start in this direction.
yes this is why I always wanted to have tests to make sure that we do not break them. Stef
-Martin
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project