[SERVER-67052] Create per action CPU metrics for linux Created: 06/Jun/22 Updated: 29/Oct/23 Resolved: 08/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Moody | Assignee: | Daniel Moody |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Dev Platform 2022-06-27, Dev Platform 2022-07-11 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
For Command line actions, we can take over the SPAWN construction variable, which will call our own spawn function and then we can tailor the command and process output before returning back to scons. For function actions we can duck-type the FunctionAction calls to execute from our own function. CPU Windows makes it a bit difficult to get this info, however chromium already has a good solution: That solution is cross platform as well. For function actions there is https://docs.python.org/3/library/time.html#time.thread_time From python, we can measure the wall clock time of the subprocess. I plan on using https://docs.python.org/3/library/timeit.html#timeit.default_timer Memory and duration metrics were completed in
|
| Comments |
| Comment by Githook User [ 08/Jul/22 ] |
|
Author: {'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}Message: |