[SERVER-49479] Create performance test for the effects of refreshes due to autosplitting Created: 13/Jul/20  Updated: 27/Oct/23  Resolved: 09/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Gone away Votes: 0
Labels: sharding-common-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-41480 Increment collection major version on... Closed
related to SERVER-49233 Introduce a flag to toggle the logic ... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

In SERVER-41480, we made a modification to the chunk versioning algorithm that caused an improvement in some scenarios, but regressions in others.

We should add a performance workload that
1) decreases the minimum chunk size to something very small;
2) performs many inserts, which will trigger autosplitting; and
3) measures latency and throughput.

We should do this for several shard key value distributions:

  • Insertions that cover the range of shard key values uniformly
  • Monotonically increasing shard keys
  • (Optional) Gaussian distribution over the range of shard key values

This would give us confidence that future changes to our versioning algorithm won't cause regressions. As part of this, we should verify that the workload would confirm the difference in performance before and after SERVER-41480.



 Comments   
Comment by Sergi Mateo Bellido [ 09/Nov/22 ]

Autosplitting was removed as part of PM-2323.

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