Create a perf workload that demonstrates a replication bottleneck based on number of oplog applier threads

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have a suspicion that increasing the number of replication oplog applier threads will help clusters in situations where the number of applier threads is the bottleneck. Right now, we don't think any of our current workloads show that bottleneck, so it's been hard to evaluate what kind of benefits a cluster can get from changing this value.

            Assignee:
            Unassigned
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: