Bouncner

FYI: struggling with the dwarf version of clang 14. GCC 11 and clang 14 generate version 5 dwarf formats, which is not supported by Valgrind. I am struggling to get...

> FYI: struggling with the dwarf version of clang 14. GCC 11 and clang 14 generate version 5 dwarf formats, which is not supported by Valgrind. > > I am...

The Valgrind issue can be reproduced and it's a false positive.

@mweisgut, @tjjordan, @dey4ss : I think I have resolved (or answered, please have a look) all review issues brought up.

Ran again into the LZ4 problems with valgrind. I do not consider this to be an issue we should solve within the LZ4 segment, as many people consider valgrind to...

I have seen some performance degradations on the AMD server, so I ran the entire benchmark twice. Unfortunately, unstable AMD results are not new to us. But anyhow, there does...

Do you use custom data or TPC-H? For TPC-H, there are out-of-the-box ways to use different encoding per column, not only table.

You can an exemplary configuration here: [simple__LPCompressionSelection_5033211488__no_fsst.json.zip](https://github.com/hyrise/hyrise/files/8351172/simple__LPCompressionSelection_5033211488__no_fsst.json.zip) With that configuration, you can call `./hyriseBenchmarkTPCH -e simple__LPCompressionSelection_5033211488__no_fsst.json` to generate and encode TPC-H data, which can then be loaded via the console...

You can use the same approach of providing a configuration JSON for the binaries `hyriseBenchmarkJoinOrder` and `hyriseBenchmarkTPCDS`. For custom data, we only have plugin-based solutions (as done in https://github.com/hyrise/encoding_selection). But...

Closing for now. Feel free to re-open any time you have questions.