[Pharo-project] Memory usage

Tudor Girba tudor at tudorgirba.com
Mon Jul 23 08:41:57 EDT 2012

The prospect sounds exciting.

Jannik, if you do manage to get this to work with Moose, it would be
great to document it :)


On Mon, Jul 23, 2012 at 2:15 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Mon, Jul 23, 2012 at 09:26:18AM +0200, jannik.laval wrote:
>> Dear pharoers,
>> We are loading really big models in the Moose software analysis platform.
>> This generate a lot of small objects and with the biggest model, we approach the limit of 2Gb of the VM.
>> Is it possible for anyone who knows the VM to add extra memory space ? Going to 4Gb or maybe 8Gb would be a great thing.
> It is possible to have an image of at least 7GB (I have done this on
> my PC with 8GB real memory). Currently this requires tracing the image
> to a 64-bit object format with SystemTracer, and running the image
> on an interpreter VM compiled for the 64-bit format.
> I expect that this will work for Moose in a Pharo image, although
> performance of the garbage collector is likely to become an issue
> as the memory grows with lots of smaller objects, and the 64-bit
> interpreter VM will be significantly slower than a 32-bit Cog VM.
> If you want to try this with one of your images, I'll try to give you
> some help.
> I believe that Eliot has longer term plans for 64-bit object formats,
> VMs, and improved garbage collectors.
> Dave


"Every thing has its own flow"

More information about the Pharo-dev mailing list