[SERVER-77835] Collect performance data for update_one w/o shard key(3 shard cluster) Created: 06/Jun/23 Updated: 29/Oct/23 Resolved: 13/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Engineering Test | Priority: | Major - P3 |
| Reporter: | Kruti Shah | Assignee: | Kruti Shah |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding NYC 2023-06-12, Sharding NYC 2023-06-26 | ||||||||
| Participants: | |||||||||
| Description |
|
For an Atlas (3 shard) sharded cluster, we want to verify the difference between the performance of a non-targeted w:majority updateOne is no more than 200% slower than a w:majority updateOne to an unsharded collection. We are using dsi to provision a 3 shard cluster(each shard with 3 nodes) and running locust scripts to insert data and perform the commands. |