[SERVER-76529] Separate execution time metric into two: one for time to first batch and one for overall time Created: 26/Apr/23  Updated: 29/Oct/23  Resolved: 06/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Naama Bareket
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77184 Look into consolidating calls to CurO... Closed
is depended on by SERVER-85099 Tracking: Milestone 1 Closed
is depended on by SERVER-85105 Tracking: PM-2885 Milestone 0 Closed
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-05-29
Participants:

 Description   

Just discussed at the six-week review, this will allow for more fine-grained insight into what might be going on.



 Comments   
Comment by Githook User [ 05/Jun/23 ]

Author:

{'name': 'Naama Bareket', 'email': 'naama.bareket@mongodb.com', 'username': 'naama-bareket'}

Message: SERVER-76529: Separate execution time metric into two: one for time to first batch and one for overall time
Branch: master
https://github.com/mongodb/mongo/commit/6124ddcb621537044688eaed08933817fcee7255

Comment by Charlie Swanson [ 26/Apr/23 ]

Proposal for names: "metrics.firstResponseExecMicros" and "metrics.totalExecMicros" (currently "metrics.queryExecMicros").

Note alyssa.wagenmaker@mongodb.com I think for non-cursor commands like the write commands in the next project we will probably only want one metric here - open to naming suggestions but maybe just "execMicros"? Or standardize on "metrics.totalExecMicros"?

Maybe there could be a difference for batched operations?

Generated at Thu Feb 08 06:32:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.