[SERVER-75658] Investigate 14% regression in mixed_findOne from telemetry Created: 04/Apr/23  Updated: 19/Apr/23  Resolved: 19/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Colby Ing Assignee: Backlog - Query Integration
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-75512 Store a hashed telemetry key rather t... Closed
related to SERVER-76042 Avoid re-parsing match, sort and proj... Closed
Assigned Teams:
Query Integration
Participants:

 Description   
task test measurement arguments z_score % change % change (stable) % change (stable to stable) evergreen_baseline_result evergreen_test_result
mixed_workloads mixed_findOne ops_per_sec {'thread_level': 512} -2.176434757 -15.40414 -12.38781578 -14.68251591 https://evergreen.mongodb.com/task/sys_perf_linux_1_node_replSet.2022_11_mixed_workloads_17965f587025e0c7dad82e396fd0d7746f92b187_23_03_29_23_14_09 https://evergreen.mongodb.com/task/sys_perf_linux_1_node_replSet_telemetry_mixed_workloads_17965f587025e0c7dad82e396fd0d7746f92b187_23_03_29_23_14_09

Investigate or fix - when we turn the flag on in master, all > 10% regressions with z_scores > 2 will trigger automatic BF creation. This test failure has > 10% regression and >2.0 z_score.

 



 Comments   
Comment by Charlie Swanson [ 19/Apr/23 ]

This was investigated and spawned the linked tickets. The flame graphs showed those areas as pretty expensive.

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