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

CopyScanCache pool size #4859

Merged
merged 1 commit into from
Mar 2, 2020
Merged

CopyScanCache pool size #4859

merged 1 commit into from
Mar 2, 2020

Commits on Feb 24, 2020

  1. CopyScanCache pool size

    Reduce max and increment size of the pool by factor of 3.4x
    
    This is effectively fixing a regression where this pool increased due to
    decrease of minimum copy cache size from 32K to 8K about a couple of
    years ago.
    
    The heuristic for the size of the pool is now based on both min and max
    size of copy cache. Relying on just min size was too conservative. If GC
    dynamically decided to use small copy caches it means that parallelism
    is low, what in turn means that scan queue is mostly empty, hence the
    need for the caches is low.
    
    Signed-off-by: Aleksandar Micic <amicic@ca.ibm.com>
    amicic committed Feb 24, 2020
    Configuration menu
    Copy the full SHA
    b9c8e2f View commit details
    Browse the repository at this point in the history