Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13070

4.2.1 Docs for SERVER-43322: Add tracking tools for measuring OplogStones performance


      Downstream Change Summary

      In this patch, we add the following server parameters: maxOplogTruncationPointsAfterStartup, maxOplogTruncationPointsDuringStartup, minOplogTruncationPoints, oplogTruncationPointSizeMB.

      We also add a section to serverStatus called "oplogTruncation", with the fields totalTimeProcessingMicros, processingMethod, truncateCount, and totalTimeTruncatingMicros. The former two fields refer to the total time necessary to process (either by sampling or by scanning) the oplog on start up in order to determine oplog truncation points. The latter two fields refer to oplog truncation count and duration.

      Description of Linked Ticket

      In order to best educate a solution for SERVER-42175, we should generate some data on start up and truncation performance with respect to different sizes of OplogStones.

      We should add server parameters for maximum counts of OplogStones and minimum sizes of OplogStones. Additionally, we should track:

      1. How long oplog sampling takes on start up
      2. Average amount of time spent truncating
      3. Cumulative length of time spent truncating
      4. Cumulative amount of truncate calls

      3. and 4. allow us to determine the average amount of time spent truncating.

      Scope of changes

      • 4.2 - WT only
      • 4.4 - WT and inMemory (DOCS-13130)

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            kay.kim@mongodb.com Kay Kim (Inactive)
            backlog-server-pm Backlog - Core Eng Program Management Team
            0 Vote for this issue
            3 Start watching this issue

              4 years, 11 weeks, 2 days ago