[SERVER-66429] Tailor Google Benchmark CI runs for correctness checks Created: 12/May/22  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Assigned Teams:
Server Development Platform
Operating System: ALL
Backport Requested:
v6.3, v6.1
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:

 Description   

Google benchmarks are for validating specific components and should not be used as regression tests. We have not identified any regressions worth fixing in the years many benchmarks have run in Evergreen.

This ticket will limit the benchmark runs to sanitizer variants as they have found correctness issues there. This change frees up resources on static and dedicated perf hosts, and reduces complexity of the Evergreen project config.


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