Phoenix vs. ClickHouse: Why the Fight Never Ends
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
Alexander Novikov compares HBase (the storage under Phoenix) and ClickHouse on the same ten million documents, tracing their differences to four storage choices: index chunk size, read unit, update rewrite and key ownership. On his single-machine stand, a whole-row point read took 0.15 ms on HBase versus 3.47 ms on ClickHouse, while a three-column scan took 0.03 s versus 24.7 s. Single-row updates took 472 µs against 81.7 ms. The figures are his own measurements and are not independently verified.