Hi guys,
I am reading the sys admin manual and it says:
Why do you recommend running both at all time if they only happen to be needed for MFC and #reclaimAll? (if I do not use epoch GC, of course) In other words...what are the drawbacks if I only start/stop them as part of my GC scripts? Thanks in advance, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Fri, Jun 19, 2015 at 7:34 PM, James Foster <[hidden email]> wrote:
Thanks James, crystal clear!!! I was just trying to see how I can minimize the memory consume while the stone/gems are not being too much used. Thanks,
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
> On Jun 19, 2015, at 3:47 PM, Mariano Martinez Peck <[hidden email]> wrote:
> > I was just trying to see how I can minimize the memory consume while the stone/gems are not being too much used. I assume that the OS will swap out inactive processes, so that shouldn’t be much of a concern. James _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Fri, Jun 19, 2015 at 7:53 PM, James Foster <[hidden email]> wrote: > On Jun 19, 2015, at 3:47 PM, Mariano Martinez Peck <[hidden email]> wrote: I was also thinking about that. Do you know is seaside gems ever get to the idle state in which the OS would swap it's memory? On the other hand, I have the seaside maintenance vm running which expires sessions every 1 hour...so maybe that task makes all seaside gems none-idle ? mmmmm _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On 06/19/2015 04:01 PM, Mariano
Martinez Peck via Glass wrote:
I am not a student of Linux swapping algorithms, but I'm pretty sure that the maintenance vm will not cause other seaside gems to "seem non-idle". The mainenance vm, will activate it's own memory pages and those pages in the SPC that are needed as well, but the private memory of other gems will not be affected ... We really try to make sure that idle gems stay idle and will only wake up when needed ... but there is at least one restless process that wakes up every 30 seconds to facilitate the handling of SigAborts ... the process itself doesn't touch much memory, but if a SigAbort is required then the gem will also do an abort and page in a bit more memory, but an abort is pretty inexpensive for a previously idle process ... BTW, this little "sigabort process" would be a spot where you could add the logic for running the periodic scavenge and mark sweep:) Dale _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |