Open jangorecki opened 1 year ago
Related: Can't we just "drop" the duckdb-latest
runs and make this the default for DuckDB
?
The duplication is a little confusing and unnecessary since the 0.9 release.
I think it is desired for duckdb team to have both version presented to compare performance between stable and devel. I would maybe suggest to trim the name so it fits better on the plots, possibly duckdb-dev
Commit https://github.com/duckdblabs/db-benchmark/commit/17d41dbdcf0f758bcab5e7e989247d4194788acc that introduced solution "duckdb-latest" is causing that the following line in run.sh https://github.com/duckdblabs/db-benchmark/blob/17d41dbdcf0f758bcab5e7e989247d4194788acc/run.sh#L66 is matching to duckdb even when duckdb is not being used, but only duckdb-latest. As a result benchmark may fail with the following message:
To resolve it we should use more precise operator than
=~
, till then let's keep this issue open in case someone will be getting such error and trying to search for it.