[SERVER-25041] Look into multi-server writeConcern latencies Created: 13/Jul/16 Updated: 08/May/23 Resolved: 08/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Replication Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | investigation, perf-improve-product, pperf | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
Most of the performance work on oplog shipping and application has been focused on improving throughput when the servers are heavily loaded with writes. The goal of this ticket is to examine and possibly improve the latency of w>1 operations (or equivalently, the throughput of single-threaded operations). An area of concern is waiting for more data before processing a batch. |
| Comments |
| Comment by Kevin Duong [ 09/Oct/17 ] |
|
redbeard0531 Was this ticket supposed to be assigned to the Performance backlog? |