Investigate disagg measure startup time variant change perf differences

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Server Integration
    • ALL
    • SESIWelcomeAlex 2026-07-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When adding more startup measurement tasks, we populated this sheet with the measurement times. We also moved to a new variant that we ran the task under. Doing so had shown our startup times drastically change from ~500s startup time for 50k collections to ~1200s for 50k collections.

      We should run the same task on the old variant to ensure that this difference in time is because of the variant change, and not some code change that introduced a regression.

      The previous variant was `Disagg 2-Node ReplSet ARM (mixed instances, Mongotune Dev Policies)`. The current variant is `Disagg 2-Node ReplSet Availability ARM (standby, Mongotune Dev Policies)`

            Assignee:
            Daniel Khuu
            Reporter:
            Daniel Khuu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: