-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Write Ops
-
None
-
Query Execution
Currently there is no information about the performance of a write in WriteResult. Having this information would be great. Here are some things that would be nice to have:
- Total execution time
- Time waiting to acquire lock
- Time holding lock
- Time waiting for replication
To clarify the last point, this would be the additional time that the primary waited to hear a replication response from a secondary in the case that a write concern > 1 is used.
- is related to
-
SERVER-18067 Add the time spent waiting for write concern in the command log line
- Closed