ClickhouseBenchmark
Why BigQuery can’t match ClickHouse Cloud for real-time analytics
Summary
ClickHouse Cloud delivered 438× better end-to-end performance per dollar than BigQuery under Capacity pricing, and 512× under On-demand pricing, while continuously ingesting 113.2 billion stock-market quotes. The CostBench methodology measures preparation cost, query cost, and query runtime as data arrives. ClickHouse Cloud led in all three components: preparation cost was 8.5× lower than BigQuery Capacity, normalized query cost was 94× lower, and accumulated query runtime was 50.8× lower. The difference originates in how each system handles incoming data: ClickHouse orders raw data and builds current summaries during inserts, while BigQuery makes new rows queryable before background clustering and materialized view refresh complete. This leaves BigQuery aggregate queries to include rows that refresh has not yet summarized, increasing cost and runtime.
Context
The post compares ClickHouse Cloud and BigQuery on real-time analytics performance using the CostBench methodology, which measures preparation cost, query cost, and query runtime while continuously ingesting 113.2 billion stock-market quotes at a target of 1 million rows per second.
Approach / What changed
ClickHouse Cloud uses asynchronous inserts to order raw data and build current summaries during ingestion, while BigQuery relies on the Storage Write API with background clustering and incremental materialized views that leave new rows queryable before refresh completes.
Takeaways
ClickHouse Cloud achieved 438× better end-to-end performance per dollar than BigQuery Capacity and 512× better than BigQuery On-demand in the CostBench real-time analytics benchmark.
ClickHouse orders raw data and builds current summaries during inserts, while BigQuery makes new rows queryable before background clustering and MV refresh complete, increasing query cost and runtime.
The CostBench methodology combines preparation cost, normalized query cost, and accumulated query runtime into a single end-to-end performance-per-dollar score.
FAQ
Why does ClickHouse prepare data faster than BigQuery?
ClickHouse Cloud uses asynchronous inserts that order raw data and build current summaries during ingestion, so queries see prepared data immediately. BigQuery makes new rows queryable while clustering and MV refresh continue in the background, so aggregate queries include rows that refresh has not yet summarized.
What hardware did each system use?
ClickHouse Cloud used a 16-CPU, 64-GiB read node. BigQuery used on-demand serverless query compute with dynamically assigned slots and no fixed reservation. The comparison is not between two fixed 16-CPU allocations.
What were the final performance-per-dollar scores?
ClickHouse Cloud delivered 438× better end-to-end performance per dollar than BigQuery under Capacity pricing, and 512× better under On-demand pricing, while ingestion and queries ran together.
Source and freshness
- Source
- clickhouse.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.