[SERVER-38917] Improve LinkBench schema to scale well with the number of shards Created: 09/Jan/19 Updated: 21/Feb/19 Resolved: 21/Feb/19 |
|
| 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: | Matthew Saltz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | ShardedTxn:LinkBench | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2019-02-11, Sharding 2019-02-25 | ||||||||
| Participants: | |||||||||
| Description |
|
It would good to see how sharded transaction throughput is affected by the number of shards. If we want to test this well, we'll need to carefully consider the LinkBench schema/shard key to make sure it makes sense/is optimal for sharding. |