Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-1966

Shared cache distribution with a single participant

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT2.7.0
    • Affects Version/s: None
    • Component/s: None
    • None

      There are cases where a shared cache configured with a max of 20GB, and a single participant. The single participant ends up being allocated only 20MB of the available space.

      Review the shared cache algorithm to ensure that a reasonable amount of space is allocated.

      The conflict here is that it's (relatively) slow to reclaim space from the shared cache, so allowing a single member to use the entire shared cache will make it slow for new members to get ramped up.

      The particular workload does single threaded inserts across several tables, whilst constantly running checkpoints.

            Assignee:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: