[SERVER-65929] Unexpected profiling overhead when classical agg runs over SBE find Created: 25/Apr/22  Updated: 29/Oct/23  Resolved: 27/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc4, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Irina Yatsenko (Inactive) Assignee: Irina Yatsenko (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: QE 2022-05-02
Participants:
Linked BF Score: 135

 Description   

Even with database profiling disabled, Linux perf profiles still show ScopedTimer and BackgroundThreadClockSource as considerable contributors (depending on the benchmark, their share might be as high as 10%).

Note: I noticed this when running $lookup benchmarks but the issue might be affecting other types of pipelines as well.



 Comments   
Comment by Githook User [ 28/Apr/22 ]

Author:

{'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}

Message: SERVER-65929 Avoid profiling overhead in aggregation over SBE find when not actually profiling

(cherry picked from commit a1f721cd6b388b590b7f7c0ed6f04578093cd8c9)
Branch: v6.0
https://github.com/mongodb/mongo/commit/03296e9bc91b1e40e66561bff6829dc3291459a2

Comment by Githook User [ 26/Apr/22 ]

Author:

{'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}

Message: SERVER-65929 Avoid profiling overhead in aggregation over SBE find when not actually profiling
Branch: master
https://github.com/mongodb/mongo/commit/a1f721cd6b388b590b7f7c0ed6f04578093cd8c9

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