Update duckdb version #6
Closed
Conversation
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
… to compare with pixels fairly.
…dataset (tpch 300). It takes a long time to finish 2. Make sure each benchmark only run once instead of running multiple times. Since we measure the IO performance, if the same query runs several times and page cache is enabled, the first execution loads the data from IO, while the subsequent executions load data from DRAM, which is not expected. 3. Print the row count of benchmark query. The duckdb benchmark would not raise an exception even if the benchmark fails. I add this for an indicator if the result runs correct or not.
Previously, duckdb used the relative path to find pixels source path, this makes the compilation unflexible.
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.
No description provided.