Prevent lukewarm cold runs in databases from Munich #659
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.
Umbra, CedarDB, and Hyper have unrealistic results in cold runs due to excessive caching.
According to the rules:
To ensure that the caches are flushed and data is actually read from disk during the cold run, I added the restart of the Docker container before the cold run of each query.
Also found that
hyper-parquetdidn't do a cache flush at all.Note: fixing this problem was suggested by puzpuzpuz #656