[SERVER-76959] Collect performance data for update_one w/o shard key on a single shard cluster Created: 09/May/23 Updated: 12/Jun/23 Resolved: 12/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: | Lamont Nelson | Assignee: | Sanika Phanse (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding NYC 2023-05-15, Sharding NYC 2023-05-29, Sharding NYC 2023-06-12 |
| Participants: | |
| Story Points: | 4 |
| Description |
|
On a cluster with a single shard we want to verify the difference between the performance of an updateOne on an unsharded vs sharded collection. We want to setup genny workloads to measure the performance for unsharded/sharded (without shard key) updates and run this on a "atlas like" instance. |
| Comments |
| Comment by Sanika Phanse (Inactive) [ 12/Jun/23 ] |