[SERVER-37697] Capture all rusage data in FTDC Server Status Created: 22/Oct/18 Updated: 29/Oct/23 Resolved: 09/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | SWDI | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2018-11-05, Service Arch 2018-11-19 |
| Participants: |
| Description |
|
We currently capture rusage but only to find hard page faults (see here). Almost all of the other fields in rusage are useful except for the maximum resident set, which we capture through the proc filesystem instead. Given that we've spent the time to make the syscall anyway, we should record the other useful info like context switches and soft faults. |
| Comments |
| Comment by Githook User [ 09/Nov/18 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |