3 ms·
DuckDB probably performs better per core than clickhouse does for most queries. So as long as your workload fits on a single machine (it's likely that it does)
by geysersam 2y ago
DuckDB probably performs better per core than clickhouse does for most queries. So as long as your workload fits on a single machine (it's likely that it does) it's often the most performant option.
Besides, it's so simple, just a single executable.
Of course if you're at a scale where you need a cluster it's not an option anymore.
- zX41ZdbW 2y agoThe good parts of DuckDB that you've mentioned, including the fact that it is a single-executable, are modeled after ClickHouse.
- RyanHamilton 2y agoCan you provide a reference for that belief? To me that's not true. They started from solving very different problems.
- geysersam 2y agoI didn't express myself well. What I meant to say was that Duckdb runs a single process. That simplifies things. Clickhouse typically runs several processes (server, clients) interacting and that already makes things more complicated (and more powerful!). That's not to say one is good and the other bad, they're just quite different tools.