[SERVER-31541] Measure CPU utilization for specific thread / connection Created: 13/Oct/17 Updated: 06/Dec/22 Resolved: 09/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | Needs Further Definition |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Dmitry Ryabtsev | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Sprint: | Service arch 2020-10-19 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Some users would appreciate if MongoDB could report CPU utilization for specific operations in db.currentOp() so they could easily identify operations that might be the candidates for further tuning. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 09/Nov/21 ] |
|
We, the Server Team, plan to address this through a related initiative. Closing & will investigate further through the initiative. |