It's fairly clear: " the Mac VM has an option -memory" no -mmap
use it or set the info.plist setting of SqueakMaxHeapSize. You can in theory set values up to 4GB on a 4.2.x VM or 5.7.x Might make lights dim and core dump on a 5.8.x VM, please try... Obviously you have to actually use the 4GB of memory. However I suspect asking for anything close to or over 5.8GB on a 4.2.x and 5.8.x VM won't fly. Should work with a 5.7.x VM On 2010-10-09, at 8:14 PM, Levente Uzonyi wrote: > On Sat, 9 Oct 2010, Max Leske wrote: > >> I'm actually working on a mac, so that shouldn't be the problem. >> So your proposition to use -mmap would be unix specific? Is the option >> available on mac? > > I don't have a Mac, but you can easily check it by starting an image with > "-mmap 64m", then allocating a 64MB array in the image. If it fails, then the > switch works, otherwise not. > > > Levente > >> >> Thanks, >> Max >> >> >> On 09.10.2010, at 21:34, Levente Uzonyi wrote: >> >>> On Sat, 9 Oct 2010, Adrian Lienhard wrote: >>> >>>> The unix VM and apparently also the Mac VM has an option -memory that >>>> allows you to set a heap size: >>>> >>>> [adrian:/Applications/Squeak 4.2.3beta1U.app/Contents/MacOS] ./Squeak\ VM\ >>>> Opt -help >>>> Usage: ./Squeak VM Opt [<option>...] [<imageName> [<argument>...]] >>>> ./Squeak VM Opt [<option>...] -- [<argument>...] >>>> >>>> Common <option>s: >>>> -help print this help message, then exit >>>> -memory <size>[mk] use fixed heap size (added to image size) >>>> -pathenc <enc> set encoding for pathnames (default: macintosh) >>>> -headless run in headless (no window) mode (default: false) >>>> >>>> Notes: >>>> <imageName> defaults to `Squeak.image'. >>>> If `-memory' is not specified then the heap will grow dynamically. >>>> <argument>s are ignored, but are processed by the Squeak image. >>>> The first <argument> normally names a Squeak `script' to execute. >>>> Precede <arguments> by `--' to use default image. >>> >>> This is ok for Mac, but the unix VM takes different arguments. >>> >>> >>> Levente >>> >>>> >>>> >>>> HTH, >>>> Adrian >>>> >>>> On Oct 9, 2010, at 18:01 , Max Leske wrote: >>>> >>>>> Hi >>>>> >>>>> I'm having trouble with low space warnings in Pharo. Is there a source on >>>>> how much memory the image can get from the OS? Is there maybe a way to up >>>>> that limit? I am loading a lot of data into the image and the limit at >>>>> the moment seems to be around 500 MB. >>>>> >>>>> Thanks for any ideas. >>>>> >>>>> Cheers, >>>>> Max >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [email protected] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <[email protected]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
