2,883 karma · joined May 23, 2016
It will be nicer if the README focuses more on per-core performance.
About the actual algorithm - will something like matching in a perfect hash table help?
https://play.clickhouse.com/docs?user=play#q=limit&name=limi...
If anyone is curious how queries in this language look, you can see it here: https://github.com/ClickHouse/ClickBench/pull/939/changes#di...
You can read more about this approach in my presentation: https://presentations.clickhouse.com/2026-openhouse-sf/great... and video: https://www.youtube.com/watch?v=FmS7VopaqNg
You can read more about this approach in my presentation: https://presentations.clickhouse.com/2026-openhouse-sf/great... and video: https://www.youtube.com/watch?v=FmS7VopaqNg
So you can create any sort of similar services in a single SQL query and an HTML page.
I also hosted it as a publicly accessible data lake, which you can query from everywhere: https://github.com/ClickHouse/ClickHouse/issues/29693#issuec...
It is also updated in real-time.
Before adding the label, we have to check the diff for suspicious things. There were a few abuse attempts (all of them were from now vanished GitHub accounts).
I've covered it in my presentation: https://presentations.clickhouse.com/2017-hash_tables/
1. Test pass rate is 99.98% is not good - the only acceptable rate is 100%.
2. Tests should not be quarantined or disabled. Every flaky test deserves attention.
It was a very frustrating experience, don't recommend anyone to try.
> 5.3 Licensee may not disclose any benchmarking or results of evaluating the Software without Exasol´s prior written consent
I was trying to add Exasol to ClickBench (https://github.com/ClickHouse/ClickBench/) since 2016, but it was not possible due to the limitations and the fact that it required using a custom virtual machine image.
Now we should try it again...