Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

force scanvenge/marksweep in idle gemServers #34

Open
dalehenrich opened this issue Jun 24, 2015 · 0 comments
Open

force scanvenge/marksweep in idle gemServers #34

dalehenrich opened this issue Jun 24, 2015 · 0 comments
Milestone

Comments

@dalehenrich
Copy link
Member

See the discussion in the mailing list for context, but long story short ... when operating with a large TOC, it is possible that when a gemserver goes idle, a significant amount of toc space will consume real memory that would normally be returned to the os if a mark sweep was run ... @marianopeck finds that the following does a good job of ensuring that idle gems consume the minimum amount of real memory:

"This thread is needed to handle the SigAbort exception, when the primary
 thread is blocked on an accept. Assuming default 60 second
 STN_GEM_ABORT_TIMEOUT, wake up at 30 second intervals."
 [
        | count minutesToForceGemGC |
        count := 0.
        minutesToForceGemGC := 30.
   [ true ] whileTrue: [
                (Delay forSeconds: 30) wait.
                count := count + 1.
                (count \\\ (minutesToForceGemGC * 2)) = 0 ifTrue: [
                        System _generationScavenge_vmMarkSweep.
                        Transcript show: 'Gem GC forced'; cr.
                        count := 0.
                        ].
        ].
 ] forkAt: Processor lowestPriority.

An extra scavenge and marksweep every thirty minutes will add a significant load on the system

@dalehenrich dalehenrich modified the milestone: 1.0.10 Jul 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant