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

Investigate why the WT lookaside score can be high when 1% of the cache is in use and no evictions occur

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: None
    • Labels:
      None
    • Story Points:
      5
    • Sprint:
      Storage Engines 2019-10-07, Storage Engines 2019-10-21

      Description

      This is a spin-off of a HELP ticket that the execution team received. The MongoDB layer was using a lookaside score threshold of 50 at the time – it has since been raised to 95 --, but it doesn't make sense why the lookaside score would be high at all when so little cache is in use.

      We were hoping you could figure out why the lookaside score when up. Perhaps delineating some kind of contract that the lookaside score follows would be helpful as well, since the MongoDB layer has become dependent on it.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              luke.pearson Luke Pearson
              Reporter:
              dianna.hohensee Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: