[SERVER-65385] Disable threshold checks for Google Microbenchmarks on DEBUG/Sanitizer variants Created: 08/Apr/22  Updated: 29/Oct/23  Resolved: 09/Aug/22

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

Type: Bug Priority: Major - P3
Reporter: Daniel Gomez Ferro Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-65359 Don't run benchmarks on DEBUG/*SAN bu... Closed
related to SERVER-65986 Disable threshold checks for highly v... Closed
is related to SERVER-62180 Enable signal processing (or red/gree... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0, v5.3
Sprint: Dev Platform 2022-05-30, Dev Platform 2022-06-13, Dev Platform 2022-06-27, Dev Platform 2022-07-11, Dev Platform 2022-07-25
Participants:
Linked BF Score: 28

 Description   

Unoptimized builds are more likely to introduce high variations on runtime. We still want to run them to catch problems with the microbenchmark code itself, but we don't want to create BFs based on performance regressions on these variants.



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

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-65385 disable analyzing benchmark results

(cherry picked from commit e9cf5fa8c7c76cfff422d6e97c549b4773d0d48e)
Branch: v6.0
https://github.com/mongodb/mongo/commit/b7380a371582c57ea3fb4447c80b205da82bfaaa

Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-65385 disable analyzing benchmark results
Branch: master
https://github.com/mongodb/mongo/commit/e9cf5fa8c7c76cfff422d6e97c549b4773d0d48e

Comment by Jeffrey Zambory [ 14/Apr/22 ]

robert.guo@mongodb.com Per Rob, this is part of the Red/Green performance waterfall. 

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