Evaluate performance of truncation marker generation and oplog growth at failover

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • RSSD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      • Evaluate performance of marker regeneration at step up for write-heavy workloads:
        • Time spent in different marker regeneration stages at step-up (stages here)
        • Typical and worst-case time to convergence
        • Typical and worst-case oplog growth over oplogSizeMB
      • Evaluate oplog size during write-heavy workload (how much the oplog exceeds oplogSizeMB)
      • Potentially evaluate performance of truncation itself, if this isn't already covered by WT team
        • This is dependent on the fast truncate project, we should reuse whatever performance approach that project uses

            Assignee:
            Unassigned
            Reporter:
            Anna Veselova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: