You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the ratio of sweeping to marking “speed”. It will be chosen to make
the GC pauses of the Sweep and Mark phases approximately equal in real-time.
This is normally larger than 1 because it turns out that the GC code needs to do
more work to mark x words of memory than to sweep the same amount. Note
that this ratio is a function of the GC code rather than the memory behaviour of
the program. We will choose a reasonable constant after studying the run-time
behaviour of the code
It'd be nice to see whether olly has enough information to measure and determine that ratio, so that we can have some realistic data on what the elapsed CPU time for marking vs sweeping is from our benchmark set, which can be used to tune that constant in the future.
(in theory the optimal constant should only depend on the GC code, and be similar across all benchmarks that use a reasonable amount of memory, but I'd expect some variation due to cache behaviour)
Activity
[-]determine GC mark vs sweep pause ratios[/-][+][enhancement] determine GC mark vs sweep pause ratios[/+][-][enhancement] determine GC mark vs sweep pause ratios[/-][+]Determine GC mark vs sweep pause ratios[/+]