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

Investigate perf impact of eviction algorithm for pages with a lot of small updates but not big enough to trigger forced eviction

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 8
    • StorEng - Defined Pipeline

      We have seen in WT-11279 that an eviction takes more than 4 minutes. It takes very long time because it has a lot of updates need to be moved to the history store. Generally, a page that has a lot of updates should have be force evicted early on when it crosses the page size threshold. However, in this page, the total size of the page is still relatively small (only half of the threshold size). Therefore, it doesn't trigger forced eviction.

      We either needs to tune of parameters or improve the eviction algorithm to help evict this kind of pages earlier to avoid the long eviction in the end.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: