Add deterministic processing mode to examples #830
Merged
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
stephenswat
added
feature
This commit adds an optional deterministic processing mode to the throughput examples. It also makes the seed configurable. The default behaviour of the examples remains as it is now, but passing the `--deterministic` flag will simply cycle through events in order, and the `--random-seed` flag allows users to configure their own random seed. If the random seed is 0 (the default) then a time-based seed is used instead.
stephenswat
force-pushed
the
feat/throughput_deterministic
branch
from
ffb0e52 to
3ff43e6
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.
This commit adds an optional deterministic processing mode to the throughput examples. It also makes the seed configurable. The default behaviour of the examples remains as it is now, but passing the
--deterministicflag will simply cycle through events in order, and the--random-seedflag allows users to configure their own random seed. If the random seed is 0 (the default) then a time-based seed is used instead.