[SERVER-3800] Add averge operation length to server status Created: 09/Sep/11 Updated: 10/Sep/11 Resolved: 10/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
For users under 100% utilization this is in some ways a more important metric than ops/sec. If at 10% util, if a change makes reads 3x slower, it won't show up in our current stats because ops/sec will remain constant. Probably best to keep total ops and total time for 10 or 100 seconds and compute avg off that. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 10/Sep/11 ] |
|
We already track total time in locks via top. |