Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simplify the heuristic for Marking and Scavenge Scan Queue splitting
defaults.
The rule is simple: one queue per 8 GC threads, which is less than what
we now use, especially for low number of threads.
This rule has already been used for allocation lock splitting with
success, for a long time.
Some more additional stress testing with Scavenger with 4x smaller
workunit (32K cache size) has been performed and no regression (lock
contention causing longer GC times) was seen.
Potential benefit of this simplification is that the cost of checking if
the global cache/packet pool is full/empty will be much lower, what will
be important for Concurrent Scavenge that will used this info as an scan
loop exit criteria.
Signed-off-by: Aleksandar Micic amicic@ca.ibm.com