Results
Every run the harness wrote to results/history/, newest first. The latest run as raw JSON: results/latest.json.
results/history/2026-10-31.json
Typical query time (geometric mean) (server-side, lower is better) on the 43 ClickBench queries over 10,000,000 rows, 5 warm runs each: ObsessionDB 64.1 ms, ClickHouse Cloud 85 ms.
| # | Contender | Status | Typical query time (geometric mean)lower is better | Full ClickBench suite timelower is better | Median query latencylower is better | p99 query latencylower is better | p99 latency with 4 concurrent clientslower is better | Data load speedhigher is better | Cost per 1,000 queries (list price)lower is better |
|---|---|---|---|---|---|---|---|---|---|
| 1 | ObsessionDB | ok | 64.1 ms | 10 s | 71 ms | 2,777 ms | 11,499 ms | 55,388 rows/s | $0.029454 |
| 2 | ClickHouse Cloud | ok | 85 ms | 11.3 s | 93 ms | 4,643 ms | 15,635 ms | 337,843 rows/s | $0.029847 |
Instance sizes
The instances differ in size; the methodology says how and which work each one favours.
- ObsessionDB: Free developer tier, single node, 4 vCPU / 8 GB RAM, eu-central
- ClickHouse Cloud: 1 replica, fixed 12 GiB / 3 vCPU (autoscaling off: min = max), AWS eu-central-1
End-to-end times at the client
Measured where the bench ran, so they include the network distance to each service. The leaderboard uses server time.
| Contender | Typical query time (geometric mean) | Full ClickBench suite time | Median query latency | p99 query latency | p99 latency with 4 concurrent clients |
|---|---|---|---|---|---|
| ObsessionDB | 134 ms | 11.6 s | 108 ms | 2,815 ms | 11,585 ms |
| ClickHouse Cloud | 138 ms | 12.6 s | 122 ms | 4,672 ms | 15,670 ms |
Environment
- runner
- Linux 6.1.188-maritime1 x64, 2 x Intel(R) Xeon(R) Processor @ 3.20GHz, 8 GB RAM
- node
- v24.22.1
- harness_commit
- 9af0bb0775b412f2bdae9fac9fca4a22df44c6be
- clickbench
- https://github.com/ClickHouse/ClickBench @ 0cb36ab1a62c445414828aae1c9dccacb71af37b (clickhouse-cloud/create.sql, clickhouse-cloud/queries.sql)
- scale
- BENCH_SCALE=10: 10 of 100 ClickBench partitioned parquet files (https://datasets.clickhouse.com/hits_compatible/athena_partitioned/hits_{0..9}.parquet)
- repetitions
- BENCH_REPETITIONS=5
- query_timeout
- 60 s
- concurrency
- 4 clients x 3 rounds, seed 20261031
- geomean
- geomean_query_ms is the geometric mean of the 43 per-query median server times (medians under 1 ms count as 1 ms)
- query_settings
- use_query_cache=0, max_execution_time=60, log_queries=1
- client
- ClickHouse HTTP interface over HTTPS, node:https with keep-alive, wait_end_of_query=1
- subject_version
- 26.8.2.1
- subject_region
- eu-central (as set up for the run; see METHODOLOGY.md)
- subject_instance
- Free developer tier, single node, 4 vCPU / 8 GB RAM
- subject_price
- $0.438356/hour, Nearest paid ObsessionDB equivalent of the free 4 vCPU / 8 GB instance: one 16 GB node (2 compute units, 4 vCPU), the smallest paid size with at least 4 vCPU and 8 GB, at the listed $20 per GB of memory per node per month = $320/month, divided by 730 hours a month (the free tier is not used as the price), read 2026-10-31 from https://obsessiondb.com/pricing
- clickhouse-cloud_version
- 26.6.1.2455
- clickhouse-cloud_region
- AWS eu-central-1 (as set up for the run; see METHODOLOGY.md)
- clickhouse-cloud_instance
- 1 replica, fixed 12 GiB / 3 vCPU (autoscaling off: min = max)
- clickhouse-cloud_price
- $0.39375/hour, ClickHouse Cloud Basic plan (its 1-replica 12 GiB / 3 vCPU size) in AWS eu-central-1: $0.2625 per compute-unit-hour (1 unit = 8 GiB / 2 vCPU) x 1.5 units, read 2026-10-31 from https://clickhouse.com/pricing