[Glass] RcIdentityBag holding deleted objects via instVar "components"?

[Dale Henrichs via Glass]

Otto,

The problem that Mariano is referring to is that with a large TOC, 
excessive RAM may be consumed by an idle gem ... When the vm runs a gc, 
and unused objects are found, the "newly freed" RAM is returned to the 
system ... you have a large TOC, so you could be exposed to the problem 
.... the large TOC is not a problem but if you frequently consume big 
chunks of the TOC and then go idel on a bunch of gems regularly running 
the in-vm gc could help ... you can probably tell if you look at vsd and 
see that an idel gem isi consuming a big chunk of RAM and once an 
in-memory gc is run the RAM drops off (not completely certain that the 
system stats in VSD represent allocated RAM or RAM that could be 
allocated ...

Dale

On 8/27/15 3:10 AM, Otto Behrens via Glass wrote:
> Can you tell if we need a workaround? We have a big problem with
> seaside service gems eating up RAM:
> GEM_PRIVATE_PAGE_CACHE_KB = 960KB;
> GEM_TEMPOBJ_CACHE_SIZE = 400000KB;
> GEM_TEMPOBJ_MESPACE_SIZE = 0KB;
> GEM_TEMPOBJ_OOPMAP_SIZE = 0;
> GEM_TEMPOBJ_SCOPES_SIZE = 2000;
> GEM_TEMPOBJ_POMGEN_SIZE = 0KB;
> GEM_TEMPOBJ_POMGEN_PRUNE_ON_VOTE = 50;
> GEM_TEMPOBJ_POMGEN_SCAVENGE_INTERVAL = 1800;
> STN_PRIVATE_PAGE_CACHE_KB = 2000KB;
> SHR_PAGE_CACHE_SIZE_KB = 2000000KB;
>
> Thanks
>
> On Wed, Aug 26, 2015 at 6:40 PM, Mariano Martinez Peck via Glass
> <glass at lists.gemtalksystems.com> wrote:
>>
>> On Wed, Aug 26, 2015 at 12:34 PM, itlists at schrievkrom.de
>> <itlists at schrievkrom.de> wrote:
>>> Am 26.08.2015 um 16:26 schrieb Mariano Martinez Peck:
>>>
>>>> BTW.... I also found that Gemstone by default does NOT enable native
>>>> code generation (JIT). I do enable it in all my gems and the difference
>>>> in performance is huge. So you may want to enable if you don't have it
>>>> ;)   (GEM_NATIVE_CODE_ENABLED=TRUE)
>>>>
>>> Reading the documentation I think, that this is enabled per default
>>> (SysAdminGuide 3.2 page 278 - default = 2 means jit enabled)
>>>
>>
>> OK, it changed then between gemstone 3.1 and 3.2.
>> If you tell me the SPC and temp space config I can tell you if it would make
>> sense a workaround we did with Dale so that "idle" gems use less memory.
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>> _______________________________________________
>> 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