ClickBench 10M: Hotdata vs Neon
Divya Ranganathan1 min read
We ran the ClickBench benchmark across 43 queries and 10 million rows (1.5 GB), comparing Hotdata to Neon.
I know it may not seem like a fair comparison to benchmark a transactional database against a columnar database. However, we've found that developers are increasingly using PostgreSQL as the primary data layer for agents because of its flexibility and ecosystem. While Postgres is great as the primary application database, when the workload shifts toward high-concurrency, low-latency search and analytical queries, a purpose-built engine like Hotdata is a better fit. This benchmark is intended to evaluate that increasingly common deployment pattern rather than compare the databases in their traditional use cases.
- Methodology: Best of 3 server-side execution times
- Hotdata:
execution_time_msfrom JSON API response - Neon:
EXPLAIN (ANALYZE, TIMING)Execution Time via direct psql
12.4s
Hotdata total time
158.3s
Neon total time
12.7×
Geomean speedup
HotdataNeon (PostgreSQL)bars: log₁₀ scale
Q
Query pattern
Hotdata & Neon execution time
Speedup
Q01
40ms
1.20s
30.0×
Q02
58ms
1.22s
21.0×
Q03
154ms
1.28s
8.3×
Q04
555ms
1.10s
2.0×
Q05
589ms
7.26s
12.3×
Q06
394ms
4.14s
10.5×
Q07
49ms
1.19s
24.2×
Q08
60ms
1.26s
21.1×
Q09
615ms
4.01s
6.5×
Q10
128ms
4.59s
35.9×
Q11
111ms
1.11s
10.0×
Q12
114ms
1.29s
11.3×
Q13
536ms
2.63s
4.9×
Q14
669ms
2.42s
3.6×
Q15
495ms
2.47s
5.0×
Q16
79ms
3.62s
45.8×
Q17
644ms
3.69s
5.7×
Q18
427ms
1.83s
4.3×
Q19
819ms
6.69s
8.2×
Q20
49ms
798ms
16.3×
Q21
334ms
1.09s
3.3×
Q22
398ms
1.25s
3.2×
Q23
776ms
1.97s
2.5×
Q24
416ms
1.11s
2.7×
Q25
124ms
1.06s
8.5×
Q26
100ms
1.20s
12.0×
Q27
136ms
1.09s
8.0×
Q28
309ms
1.80s
5.8×
Q29
1.26s
15.6s
12.4×
Q30
94ms
3.31s
35.2×
Q31
150ms
7.64s
50.9×
Q32
169ms
8.54s
50.5×
Q33
184ms
27.9s
151.7×
Q34
307ms
8.32s
27.1×
Q35
305ms
8.99s
29.5×
Q36
90ms
2.68s
29.8×
Q37
109ms
1.74s
16.0×
Q38
71ms
1.61s
22.7×
Q39
89ms
1.22s
13.7×
Q40
158ms
1.73s
11.0×
Q41
68ms
1.62s
23.9×
Q42
59ms
1.63s
27.6×
Q43
57ms
1.32s
23.1×