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

Scan Queue splitting defaults #4780

Merged
merged 1 commit into from
Jan 29, 2020

Commits on Jan 28, 2020

  1. Scan Queue splitting defaults

    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>
    amicic committed Jan 28, 2020
    Configuration menu
    Copy the full SHA
    6b41925 View commit details
    Browse the repository at this point in the history