Allow backoff to not penalize all workloads in mixed mode #4564
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sadhansood
force-pushed
the
sadhan/workload_disjoint_mode
branch
from
ba61fa6 to
6dccdf7
Compare
longbowlu
approved these changes
Sep 12, 2022
sadhansood
force-pushed
the
sadhan/workload_disjoint_mode
branch
from
6dccdf7 to
0bd4dfe
Compare
* Fix metric collection for network client in stress test * Cleanup old benchmark code
sadhansood
force-pushed
the
sadhan/workload_disjoint_mode
branch
from
0bd4dfe to
8580145
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the current testnet setup, we noticed a couple times when shared counter workload completely stop making progress that it affected the transaction throughout of transfer object workload. This is because the backoff in load gen considers total pending requests across all workloads before deciding to send a request. We aim to fix this behavior by adding a new mode (disjoint_mode) where different workloads run completely independently such that even if one is completely dead, the other keeps making progress as expected.