[SERVER-72191] sample_rates.js should use actual traffic instead of target traffic to calculate the expected number of sampled queries Created: 16/Dec/22  Updated: 29/Oct/23  Resolved: 05/Jan/23

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

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2023-01-09
Participants:
Linked BF Score: 20

 Description   

This test currently doesn't account for actual network conditions. It uses the expected (i.e. target) number of queries per second to calculate the expected number of queries per second. This has caused the actual number of sampled queries to sometimes be very off from the expected as can be seen in BF-26996 and BF-27198. Therefore, the test should use actualNum{Find,Delete,Agg}PerSec instead of the targetNum{Find,Delete,Agg}PerSec to calculate expected{Find,Delete,Agg}Count.



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

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-72191 sample_rates.js should use actual traffic instead of target traffic to calculate the expected number of sampled queries
Branch: master
https://github.com/mongodb/mongo/commit/482a1eb57f4348ef8e3e1d767ce4d49d1b271086

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