[SERVER-2018] Tracks faults during write/read lock separately Created: 27/Oct/10 Updated: 24/Feb/17 Resolved: 24/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Tools, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The performance ramifications of a fault during a read or a write is significant and it would be helpful to track these separately. It would be good to track these in mongostat and with the serverStatus command. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/10 ] |
|
This is complex and will get nearly impossible with concurrency improvements we're planning. |