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

Evaluate whether to consider internal pages for dirtied by a transaction

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

      WT-10027 modified the code which now looks as follows:

               * For application threads, track the transaction bytes added to cache usage. We want to
               * capture only the application's own changes to page data structures. Exclude changes to
               * internal pages or changes that are the result of the application thread being co-opted
               * into eviction work.
              if (!F_ISSET(session, WT_SESSION_INTERNAL) &&
                F_ISSET(session->txn, WT_TXN_RUNNING | WT_TXN_HAS_ID) &&
                __wt_session_gen(session, WT_GEN_EVICT) == 0)
                  WT_STAT_SESSION_INCRV(session, txn_bytes_dirty, size);

      The comment says to exclude the changes to the internal pages, but the code includes them. This ticket will explore whether to fix the comment or the code.

      cc sue.loverso@mongodb.com

            backlog-server-storage-engines Backlog - Storage Engines Team
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            0 Vote for this issue
            5 Start watching this issue