evergreen
Why ClickHouse wants your inserts in batches
Every INSERT into MergeTree creates a part on disk. Feed it row-by-row and you trade write throughput for a merge storm — batch, or let async inserts batch for you.
3 min#clickhouse#performance
/ #clickhouse
ClickHouse
🧪 Sample hub. Placeholder intro demonstrating topic hubs — edit or delete via /admin → Topic hubs.
Notes on the operational side of ClickHouse: how MergeTree actually behaves under write pressure, what the replication log costs, and the habits that keep hundreds of thousands of rows per second from becoming a merge storm. Start with the batching note — everything else builds on it.
1 note