Matching simulation with more read partitions than write partitions #6229
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Adding a new matching simulation scenario to measure the impact of having more read partitions than write partitions on a tasklists.
vs
Why?
This comparison is interesting because tasklist partition increments are done in phases where first read partitions are increased and then write partitions are increased to the same. During that period, the poll requests routed to the partitions without any write activity would not find any tasks and must be forwarded to parent partition in order to find a task.
How did you test it?
Ran
./scripts/run_matching_simulator.sh more_read_partitions
and./scripts/run_matching_simulator.sh default
.Highlights from the results:
Conclusion: Having more read partitions than read partitions clearly impacts the p99 task latencies and sync match rate in a negative way.