[Glass] Gemstone for OSX - VM temp obj space full when updating GLASS

James Foster james.foster at gemtalksystems.com
Thu Oct 3 12:39:20 PDT 2013


Good point. Dale also pointed out that I could use $GEMSTONE/seaside/system.conf as a template for the config file so we get other configurations. I'll do that shortly.

James

On Oct 3, 2013, at 12:37 PM, Jupiter Jones <jupiter.jones at mail.com> wrote:

> Thanks James,
> 
> I like the new setEnv.sh - if we create a seaside extent, can $GEMSTONE/seaside/bin also be added to the path?
> 
> Thanks again.
> 
> Cheers,
> 
> Jupiter
> On 03/10/2013, at 1:08 PM, James Foster <James.Foster at GemTalkSystems.com> wrote:
> 
>> I have uploaded GemStone.app 1.2.2 that specifies a 100 MB GEM_TEMPOBJ_CACHE_SIZE. I still plan to make it configurable, but this should be reasonable for most uses and can still be changed by editing the config file manually after starting the stone.
>> 
>> James
>> 
>> On Oct 2, 2013, at 4:03 PM, James Foster <james.foster at gemtalksystems.com> wrote:
>> 
>>> If you use Topaz, then the TempObjCacheSize is managed from the command line. If you use GemTools, then it is managed elsewhere and the the default TempObjCacheSize of 10 MB is much too small. In the screencast (https://www.youtube.com/watch?v=dnRB5rBbkiI) from 2:00 to 2:30 I demonstrate how to edit the config file so that it has a larger space. Basically, you need to edit ~/Library/GemStone/db1/etc/system.conf so that the last line is not commented out and has a larger value (say, 100 to 150 MB or 100000 to 150000 KB). 
>>> 
>>> At the moment you will need to edit this file after starting the database (we recreate the file each time we start). I plan to add the desirable TempObjCacheSize as a configuration that is managed through the app, but that isn't done yet.
>>> 
>>> James
>>> 
>>> On Oct 2, 2013, at 3:54 PM, Paul DeBruicker <pdebruic at gmail.com> wrote:
>>> 
>>>> I may have a setting wrong but if I start a new 3.1.0.4, initialize a GLASS  extent and begin to update GLASS to 1.0beta9.1  through GemTools I get a 
>>>> 
>>>> "VM temporary object memory is full 
>>>> , almost out of memory, too many markSweeps since last successful scavenge"
>>>> 
>>>> error.  If I set the object cache to 1024 and the temp cache to 500 then it still happens.  What should I try next?
>>>> 
>>>> 
>>>> Thanks
>>>> 
>>>> Paul
>>>> _______________________________________________
>>>> Glass mailing list
>>>> Glass at lists.gemtalksystems.com
>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>>> 
>> 
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 



More information about the Glass mailing list