[SERVER-46921] Make tracking of timing information in PlanStage opt-in Created: 17/Mar/20  Updated: 29/Oct/23  Resolved: 13/Apr/20

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45406 Provide ExpressionContext in PlanStag... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-03-23, Query 2020-04-06, Query 2020-04-20
Participants:

 Description   

Forked from SERVER-45406. It looks like we can get a substantial performance improvement by not collecting stats/timing info in the PlanStage layer when we don't have to.



 Comments   
Comment by Githook User [ 13/Apr/20 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}

Message: SERVER-46921 make collection of timing info opt in in PlanStage
Branch: master
https://github.com/mongodb/mongo/commit/5388b23cb85e84eb4ce5a2c03b250e62ff89ea1f

Comment by Githook User [ 13/Apr/20 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}

Message: SERVER-46921 make collection of timing info opt-in on PlanStage
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/b819cb433ec7f0649833cd4ffd235295312a52ff

Generated at Thu Feb 08 05:12:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.