Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Jsonbench is back and clickhouse still leads
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

JSONBench is back, and ClickHouse still leads

Source: ClickHouse•November 16, 2026 at 09:44 AM

JSONBench is back, and ClickHouse still leads

JSONBench now compares 27 database engines. ClickHouse still leads on a billion JSON documents. Explore the results and run the benchmark yourself.

JSON is the lingua franca for handling semi-structured and unstructured data in modern systems, powering everything from logging and observability to real-time streaming, mobile app storage, and machine learning pipelines.

Document databases such as MongoDB make it easy to start working with JSON. Once the server is running, you can insert documents without declaring their fields or types upfront. The documents don’t have to share the same structure. Getting started feels refreshingly simple.

ClickHouse can do this too. Create a table with a single JSON column, and you can start ingesting documents as they arrive, whatever their structure is, without defining the fields inside them upfront.

The first documents are easy. Now let’s run an aggregation over a billion documents in MongoDB and ClickHouse.

The query below comes from JSONBench, our open-source benchmark for analytics on JSON.

For this test, we use real Bluesky events with their original nested JSON structure, rather than the simplified posts above. Each document represents an event such as a post, like, or repost. We’ll count which event types occur most often.

The corresponding MongoDB query:

The ClickHouse query:

The result is a list of event types and their counts, ordered from most common to least common.

ClickHouse returns the result in 661 ms on the cold run. MongoDB takes 32 minutes and 26 seconds. Both run on the same machine type, using the published benchmark configurations. The hot runs are shown alongside them.

ClickHouse brings its native columnar storage, compression, and parallel query engine to JSON. Documents retain their flexibility, while queries benefit from reading and processing the fields they need.

We introduced JSONBench in January 2025 with five systems: ClickHouse, MongoDB, Elasticsearch, DuckDB and PostgreSQL. Each was tested on the same Bluesky data with five analytical queries.

In the original comparison, ClickHouse consistently outperformed all other tested JSON data stores in query performance and storage efficiency. Analytical query speedups reached thousands of times, while the stored JSON was even smaller than the compressed source files.

The charts use JSONBench’s combined score, which brings together hot and cold query runtimes, loading time and storage size. Lower is better. The historical chart applies today’s calculation to the original measurements, omitting loading time because it was not recorded then.

The competition has had almost two years to catch up. Alexey Milovidov, the inventor of ClickHouse, has now revived JSONBench, merged community contributions and added more systems. The original five have been retested with newer versions and updated configurations. ClickHouse still leads their billion-document comparison.

The field has grown from five to 27 database engines, including OpenSearch, Apache Doris, Databend, SingleStore, SQLite, and Umbra. The next chart shows 14 selected entries with billion-document scores on the same machine type. ClickHouse leads this broader comparison too.

The current charts show Combined scores relative to ClickHouse at 1.0. Lower is better. These are benchmark scores, not query time multipliers; unsuccessful queries and incomplete loads receive penalties.

Since the original JSONBench, we’ve shipped 178 changes to ClickHouse’s native JSON type, covering performance improvements, new features and fixes.

That includes faster reads and lower memory use, new indexes over JSON field names and values, direct JSON support in Parquet, and the option to add type hints without rewriting historical data.

The chart below shows JSON pull requests in yellow and work on the supporting Dynamic type in gray. Dynamic preserves the original types when a JSON field contains different kinds of values across documents.

And we’re not done. The JSON umbrella issue tracks ongoing work and welcomes feature requests.

JSONBench is now also part of our Versions Benchmark, where you can follow JSON query performance across releases.

JSONBench is an open-source benchmark with public data, queries, configurations and results. You can reproduce the measurements, inspect how each system is tested, and contribute improvements.

If you know a system can do better, contribute an improved configuration or query. If your database is missing, add it. Vendors and community contributors are welcome.

JSON is the lingua franca for logs, events, applications, and machine learning pipelines. ClickHouse combines the flexibility to store those documents as they arrive with fast analytics and efficient storage at scale. That gives people and agents a common analytical engine for the applications they build, the systems they observe, and the security events they investigate.

← All articles

What this article says

More in Data & Analytics

All →
How ISVs are unlocking European workloads on Google Cloud Dedicated
Looker

How ISVs are unlocking European workloads on Google Cloud Dedicated

Inside the new Data Boundary experience
Looker

Inside the new Data Boundary experience

Every flag needs evidence: how ReviewerZero AI traces integrity issues back to the page
Datalab

Every flag needs evidence: how ReviewerZero AI traces integrity issues back to the page

How I built my next career chapter at Amplitude
Amplitude

How I built my next career chapter at Amplitude

What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more
Grafana Labs

What's new in Pyroscope: profile more of your workflows, troubleshoot with AI agents, and more

How Connected Insight Can Guide a Complete Wildfire Strategy
Verisk

How Connected Insight Can Guide a Complete Wildfire Strategy

More from ClickHouse

Introducing Loom: agent memory that keeps up with your code
ClickHouse

Introducing Loom: agent memory that keeps up with your code

SET allow_preview_features = 1: Self-service previews in ClickHouse Cloud
ClickHouse

SET allow_preview_features = 1: Self-service previews in ClickHouse Cloud

Bring high-performance analytics to your lakehouse with ClickHouse and Amazon S3 Tables
ClickHouse

Bring high-performance analytics to your lakehouse with ClickHouse and Amazon S3 Tables

ClickHouse Managed Postgres goes GA and Xata acquisition brings agentic capabilities to the service
ClickHouse

ClickHouse Managed Postgres goes GA and Xata acquisition brings agentic capabilities to the service

The largest expansion of ClickHouse yet
ClickHouse

The largest expansion of ClickHouse yet

Langfuse launches AI Gateway
ClickHouse

Langfuse launches AI Gateway