Merged
Conversation
* path to database can be parametrized * do separate warmup and benchmark loops (so JIT can kick in) * use fixed random seeds for repeatable runs
Member
|
Thanks. These are definitely big improvements to the benchmark. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Benchmark results might vary based on a number of factors. I tend to select a fixed random seed so the test run is repeatable. Also, I disable Intel's Turbo Boost feature, so it doesn't vary the CPU frequency with overclocking. I run the benchmark loop multiple times, so the JIT is warmed up. With these tweaks, you get more consistent and meaningful results.