[SERVER-65366] Review the variability of the sharding benchmarks Created: 08/Apr/22 Updated: 05/Dec/22 Resolved: 12/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sharding-product-sync | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Participants: | |||||||||
| Description |
|
This task is a placeholder to discuss about what to do with the sharding benchmarks. Some context: recently some safety checks were introduced to the benchmarks to verify that we don't add performance drops of more or equal than a 20%. The problem seems to be that our benchmarks have a huge variability and because of that we are generating a bit of redness on EVG. |