Why We Didn't Converge: ClickHouse's VLDB Paper and the Architecture Agents Actually Need

The moment ClickHouse writes CPU code for your query You run SELECT category, COUNT(*) FROM events GROUP BY category against 100 million rows. On most databases, the engine walks a bytecode interpreter row by row, dispatching through a switch statement for every tuple. ClickHouse does something else. It takes your specific aggregation, hands it to LLVM, and generates native x86-64 instructions for this exact query. Then it runs them. The difference is 2 seconds versus 12 seconds. Same hardware,