Docs: Add --without-daemon flag to benchmark script
#5839
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
ltalirz
approved these changes
Dec 17, 2022
docs/source/howto/include/scripts/performance_benchmark_base.py
Outdated
Show resolved
Hide resolved
The benchmark script sends a number of `ArithmeticAddCalculation`s to the daemon and reports the time taken per process at the end. This is intended for users to run to get an idea of the performance of their setup. However, running over the daemon is not necessary the most straightforward when it comes to analysing the results and the timings can differ quite a bit. It makes more sense to simply run the N jobs serially, which should give a better more consistent picture of the average overhead per process.
sphuber
force-pushed
the
feature/benchmark-script-without-daemon
branch
from
b8ec5e8
to
788cd24
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.
The benchmark script sends a number of
ArithmeticAddCalculations to the daemon and reports the time taken per process at the end. This is intended for users to run to get an idea of the performance of their setup. However, running over the daemon is not necessary the most straightforward when it comes to analysing the results and the timings can differ quite a bit. It makes more sense to simply run the N jobs serially, which should give a better more consistent picture of the average overhead per process.