Back to Feed
Tuesday, Sep 1, 2026, 03:00 PM

Log Analytics Evolution: CtrlB Outpaces ClickHouse on ClickBench and 5TB Dataset

Log Analytics Evolution: CtrlB Outpaces ClickHouse on ClickBench and 5TB Dataset

A recent breakthrough in log analytics performance has caught the attention of the SRE and DevOps community. A benchmarking report published by the creators of CtrlB demonstrates remarkable performance advantages over ClickHouse, a long-time industry standard for analytical database workloads.

The Benchmarking Results

For years, infrastructure teams have maintained separate systems for dashboards (analytical queries) and log search (point lookups) because no single engine could excel at both. CtrlB set out to challenge this paradigm, putting its engine to the test across two distinct benchmarks:

  1. Analytical Performance (ClickBench): On a 100-million-row unpartitioned web analytics dataset, CtrlB secured the #1 spot on the single-node Parquet leaderboard with a score of 1.43×, outperforming DuckDB (1.49×), DataFusion (1.71×), and ClickHouse itself (1.72×).
  2. Full-Text Search (5 TB of Raw Logs): SREs rarely query logs just for analytics; they need to find specific trace IDs. In a cold-cache lookup test of 8 complex queries over 5 TB of raw logs, CtrlB beat ClickHouse v26.2 on every single query, ranging from 2.2× faster on double substring matches to a staggering 98.9× faster on span ID lookups.

Why This Matters for SREs and MTTD

In modern reliability engineering, every second spent waiting for a query to complete during an active incident directly inflates your Mean Time to Detection (MTTD) and Mean Time to Resolution (MTTR). Finding a needle in a 5 TB haystack in seconds rather than minutes can be the difference between a minor blip and a breached SLA.

Building a Resilient Monitoring Strategy with Rabbit SaaS

Upgrading your analytical engines to cutting-edge technologies like CtrlB is only half the battle. To ensure end-to-end reliability of your ingestion pipelines and public trust, SRE teams rely on the Rabbit SaaS suite:

  • Prevent Ingestion Gaps with Cron Rabbit: Large-scale log engines rely heavily on cron-based batch ingestion pipelines, log-rotation daemons, and S3 backup syncs. If these silent background processes fail, your fast new database won't have the data it needs. Cron Rabbit monitors these jobs via simple heartbeat curl pings, alerting you immediately if a backup or ingestion script stalls.
  • Keep Users Informed via Status Navigator: Infrastructure migrations—such as moving from ClickHouse to CtrlB—can occasionally cause planned or unplanned downtime. Status Navigator provides custom-branded, highly resilient incident status pages to maintain customer trust, shielding your core infrastructure from API flood during degradations.
  • Track Upstream Dependencies with CloudStatusHQ: If your log platform runs on managed cloud infrastructure or uses third-party analytics integrations, CloudStatusHQ aggregates vendor health statuses into a single pane of glass so you always know if an outage is internal or cloud-provider related.

As data volumes grow, optimizing both your storage engines and your operational monitoring safeguards your platform against unexpected downtime.