undefined | Better HN

0 pointsgeysersam1y ago0 comments

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.

0 comments

zX41ZdbW1y ago

The good parts of DuckDB that you've mentioned, including the fact that it is a single-executable, are modeled after ClickHouse.

RyanHamilton1y ago

Can you provide a reference for that belief? To me that's not true. They started from solving very different problems.

geysersamOP1y ago

I 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.

j / k navigate · click thread line to collapse