Investigate latency regressions in resharding workload while in catalog shard mode

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC
    • Sharding NYC 2023-06-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As part of SERVER-74266 we ran a genny workload patch with catalog shard mode on for the `shard` and `shard-single` suites. The results of the patch can be found here: https://spruce.mongodb.com/version/64346dd05623438f7351377a/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

      Using the performance analyzer tool to analyze the patch, we found that the reshard_collection_mixed workload had the largest regressions in terms of latencies. More specifically there were significant regressions in the 99th percentile latencies for reads and writes to a collection being resharded. 

      The following is a mini-writeup with more details on the genny workload patch and the specific regressions noticed: https://docs.google.com/document/d/1eAioYLvz_haug2RkRx-5e9Dlscw-nT8xQ70WNWmkSag/edit?usp=sharing

      Someone with knowledge on resharding should investigate these regressions and see if there is anything that needs to be fixed or improved. 

            Assignee:
            Wenqin Ye
            Reporter:
            Wenqin Ye
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: