ZXzX41ZdbW·Nov 3, 2025
I'm trying to make Turso load some data, but it is so slow that even several months are not enough to load the dataset: https://github.com/ClickHouse/ClickBench/issues/336
In Notes by djb on using Fil-CClickHouse
ClickBench
Shell2022–2026
ClickHouse / ClickBench
ClickBench
ClickBench: a Benchmark For Analytical Databases
33Distinct people
73Mentions
1Explicit recommenders
1.2KGitHub stars
What to know before exploring
What it is
ClickBench: a Benchmark For Analytical Databases
GitHub
Where it is used
- rtabench — RTABench uses the Clickbench framework for benchmarking, but it introduces a new dataset and query set that better represents real-time analytics inside applications. All tools, datasets, and benchmark results are available on GitHub, where we welcome contributions for expanding RTABench to support additional databases and optimizations. Source
What people are saying
Also I recommend to read the methodology here: https://github.com/ClickHouse/ClickBench/blob/main/README.md Making an open-source, easily reproducible benchmark with clear…
zX41ZdbW used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:03:49 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year73 dated mentions
Observed mentions: 2022-07-13 16:03:09 UTC to 2026-11-02 01:46:48 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 20 | 0 | 20 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 27 | 1 | 26 |
What Hacker News says
8 sourcesI don't think that's right, it looks to be a set of 43 queries with zero joins: https://github.com/ClickHouse/ClickBench/blob/main/versions/...
In ClickHouse raises $350M Series CYeah I think that's a good summary. For instance, clickbench is comprised of >40 queries and there's not a single join in them: https://github.com/ClickHouse/ClickBench/blob/main/clickhous...
In ClickHouse raises $350M Series Cpeople tried to run spark (better hadoop) and failed lol. https://github.com/ClickHouse/ClickBench/pull/139
In Postgres Just Cracked the Top Fastest Databases for AnalyticsPipe-based query syntax has been appeared a better alternative to SQL in many databases, because it is easier to read, write and maintain. The only thing is that this syntax isn't standardized among databases yet.
BTW, we at VictoriaLogs also use pipe-based syntax for LogsQL query language [1] since the first release in 2023. Recently I wrote an SQL -> LogsQL conversion guide [2], which has been appeared quite clear and easy to follow. This guide was written during the conversion of SQL queries to LogsQL at ClickBench benchmark from ClickHouse [3].
[1] https://docs.victoriametrics.com/victorialogs/logsql/
[2] https://docs.victoriametrics.com/victorialogs/sql-to-logsql/
[3] https://github.com/ClickHouse/ClickBench/tree/main/victorial...
In SQL pipe syntax available in public preview in BigQuerySome examples from me:
Database benchmarks: https://github.com/ClickHouse/ClickBench (containing 30+ databases) and the new JSON analytics benchmark, https://github.com/ClickHouse/JSONBench/
Plus, the hardware benchmark: https://benchmark.clickhouse.com/hardware/ (also used by Phoronix).
In Backblaze Drive Stats for 2024Pay attention that VictoriaLogs doesn't need any configuration and table schema in this benchmark - it is enough to ingest JSON lines, where every line contains a single ad serving event [1].
Also it is interesting to compare the original SQL queries [2] to LogsQL queries [3]. LogsQL queries are shorter and they are easier to understand even if you aren't familiar with LogsQL. See how to convert SQL to LogsQL [4].
[1] https://github.com/ClickHouse/ClickBench/tree/main/victorial...
[2] https://github.com/ClickHouse/ClickBench/blob/main/clickhous...
[3] https://github.com/ClickHouse/ClickBench/blob/main/victorial...
[4] https://docs.victoriametrics.com/victorialogs/sql-to-logsql/
In VictoriaLogs Beats Elasticsearch, MongoDB and PostgreSQL in ClickBenchVictoriaLogs Beats Elasticsearch, MongoDB and PostgreSQL in ClickBench
Hi, I'm the core developer of VictoriaLogs - zero-config schemaless open-source database for logs. Recently I tried running ClickHouse benchmark on it [1]. This benchmark executes various analytical queries over a table with 100 million rows. Every row represents an ad serving event with ~100 different fields such as UserID, ClientIP, AdvEngineID and so on. You can look at the table definition at [2].
Why running analytical benchmark against database for logs? VictoriaLogs is designed as a database for logs. It supports both plaintext and structured logs. Structured logs can be written to a single table with pre-defined columns for every field seen in the structured logs. So rows with ad serving events from ClickBench can be treated as structured logs with many fields. Such logs are known also as wide events [3].
VictoriaLogs has some opt
Read the rest
imizations for wide events. For example, it stores data per each column in distinct blocks on disk (aka column-oriented storage). This allows reading data only for the needed columns during query execution. That's why I decided giving VictoriaLogs a try at ClickBench [4].
It has been appeared that VictoriaLogs shows good results there:
- it needs 4.5x less disk space than Elasticsearch and PostgreSQL, and 5x less disk space than MongoDB
- it loads data 4.7x faster than Elasticsearch and 21x faster than MongoDB
- it executes queries 9.3x faster than Elasticsearch, 111x faster than PostgreSQL and 51x faster than MongoDB on average
You can easily run and reproduce the benchmark on your hardware by cloning ClickBench [5] and executing benchmark.sh script per each database you want to test (each benchmark.sh script is located in the folder with the corresponding database name).
[1] https://benchmark.clickhouse.com/
[2] https://github.com/ClickHouse/ClickBench/blob/main/clickhouse/create.sql
[3] https://jeremymorrell.dev/blog/a-practitioners-guide-to-wide-events/
[4] https://github.com/ClickHouse/ClickBench/tree/main/victorialogs
[5] https://github.com/ClickHouse/ClickBench