Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clickhouse to regression script #69

Merged
merged 22 commits into from
Dec 8, 2023

Conversation

Tmonster
Copy link
Collaborator

@Tmonster Tmonster commented Dec 4, 2023

Add click house to the regression script as well.

@Tmonster Tmonster merged commit d41999f into duckdblabs:master Dec 8, 2023
16 checks passed
Copy link

@qoega qoega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will try not to use TEST_RUN hack in my PR. Will we see that it works without it in my PR?

install_solution("datatable")
elif solution == "clickhouse":
install_solution("clickhouse")
install_solution("polars")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why polars in needed? Just a typo?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

polars was needed because clickhouse outputs NA as a result in the time.csv file. The current verification script throws these out before checking that all results are the same. If only clickhouse is run, then the results are empty after NA is thrown out. So if I add polars then there are still query results that can be verified. Polars was chosen because it installs quickly and runs quickly.

Feel free to modify how clickhouse writes to time.csv to fix this. It doesn't have to be in this PR though, can be later

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clickhouse/clickhouse-parse-log.R

This is the place to fix it

Comment on lines +58 to +59
# needed because clickhouse for some reason produces an error the first
# time a benchmark is run. The next benchmark run will work and overwrite the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's check if it remains after my PR will be merged. I think it will be not necessary(or I will check what happens)

@Tmonster
Copy link
Collaborator Author

Tmonster commented Dec 8, 2023

I will try not to use TEST_RUN hack in my PR. Will we see that it works without it in my PR?

TEST_RUN is only used for Spark currently. It is used to modify certain settings so that the benchmark can run on a GitHub actions machine. Spark will fail if the memory limit is set to 250GB on a GitHub actions machine. I don't think it modifies anything in the click house script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants