[SERVER-51669] Improve accuracy of computation of 'executionTimeMillisEstimate' values in explain output Created: 15/Oct/20 Updated: 27/Jun/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mihai Andrei | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, the executionTimeMillisEstimate field in the output for explain can be very inaccurate, particularly with queries whose individual operations are on the order of microseconds (see the discussion on HELP-19145 for more details). This ticket tracks the work necessary to improve the accuracy of this estimate. |