[SERVER-69056] 'explain' should include actual resource consumption costs when run with verbosity 'executionStats' Created: 22/Aug/22 Updated: 29/Oct/23 Resolved: 18/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Adi Agrawal |
| 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: | QE 2022-11-14, QE 2022-11-28 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Original title: 'explain' should include estimated resource consumption costs Example:
Actual implementation: When explain is run with verbosity executionStats or higher, the "executionStats" now contain "operationMetrics" as well if profileOperationResourceConsumptionMetrics is enabled. These operationMetrics show runtime stats, if they are not zero. The stats are nested within "operationMetrics" which is nested in "executionStats." They include: "cpuNanos" |
| Comments |
| Comment by Githook User [ 18/Nov/22 ] |
|
Author: {'name': 'Adityavardhan Agrawal', 'email': 'aa729@cornell.edu', 'username': 'Adityav369'}Message: |
| Comment by Kyle Suarez [ 28/Oct/22 ] |
|
On discussion with bernard.gorman@mongodb.com at our director triage:
Removing this from director triage and assigning to myself to find an assignee. |
| Comment by Ana Meza [ 25/Oct/22 ] |
|
bernard.gorman@mongodb.com kyle.suarez@mongodb.com could you assign this to someone? |
| Comment by Will Huang [ 24/Oct/22 ] |
|
Hi team, it would be helpful for serverless usage investigations to have this option available when running the explain command for a given query. This would be quite useful for customer's serverless usage investigation related cases. |
| Comment by Eric Milkie [ 12/Sep/22 ] |
|
It would look similar as the example above; the operationMetrics field would be at the top level. Ideally the non-winning plans that the command attempts would not be included in this. brenda.rodriguez@mongodb.com I would say this is required for Serverless. |
| Comment by Vishal Dhiman (Inactive) [ 09/Sep/22 ] |
|
milkie@mongodb.com Yes, this will be very useful. What will the output look like for IXSCAN?
|
| Comment by Eric Milkie [ 09/Sep/22 ] |
|
vishal.dhiman@mongodb.com do you think this is a feature we should include for Serverless? I can imagine users taking advantage of this to know how much an individual query can cost. I don't think there is currently any other way for a user to see this information. |
| Comment by Brenda Rodriguez [ 06/Sep/22 ] |
|
milkie@mongodb.com and kateryna.kamenieva@mongodb.com could you please let us know if this is required for server less and belongs in an epic or if it's just a "nice to have?" Thanks! |