Beats Spark
on the public benchmarks.
Every query. Open methodology. Run it yourself.
PERIOD.
All 43 queries. Nothing hidden.
ClickBench is a public third-party benchmark for analytical query engines, maintained by the ClickHouse team and open to entries from any system. Forty-three queries against a real-world web analytics dataset. Lower time = faster. Hardware: AWS c6a.4xlarge, single node, Parquet.
Sail at scale. Distributed TPC-DS at 3TB and 1TB.
Sail ran derived TPC-DS at 1TB and 3TB on a distributed cluster, streaming shuffle over Arrow Flight without writing it to disk.
- Cluster
- 8 × r8gn.8xlarge
- Compute
- 256 vCPU · 2 TiB memory
- Data
- Parquet on S3
- Shuffle on disk
- None
Faster than published TPC-DS results for Spark and Spark accelerators on similar hardware and settings.
Read the full benchmark →Derived TPC-DS, not an official TPC result. Comparison sources are linked in the write-up.
Verified by people who built the underlying stack.
LakeSail is built on Apache Arrow and Apache DataFusion, the same open-source engine infrastructure that powers a generation of fast analytical systems. The people who built those foundations have reviewed our work.
LakeSail embodies the best next generation lakehouse architecture, combining native performance with managed ease of use. A compelling platform for data intensive applications.
Run it yourself.
Every step is open.
The Sail entry in ClickBench is open and runnable end-to-end. Install script, data loader, queries, and per-run results all live in one directory on GitHub. If you can reproduce a result, you can trust it.
The commands below reproduce the 2026-10-01 c6a.4xlarge Sail run on a fresh Ubuntu host. See benchmark.sh for the canonical flow.
# Reproduce on AWS c6a.4xlarge, Ubuntu git clone https://github.com/ClickHouse/ClickBench cd ClickBench/sail ./install # Sail + deps (Rust, Python 3.11, pysail) ./load # no-op: Sail reads hits.parquet directly ./benchmark.sh # ~14 GB; 43 queries x 3, best of 3 -> result.csv # Published run: results/20261001/c6a.4xlarge.json
From benchmark results
to your actual bill.
Beyond raw speed, the same workload costs dramatically less to run. The numbers below come from a separate derived TPC-H run on a larger dataset, where Sail finished the workload 10x faster and peaked at 26 GB of memory, small enough for an instance 1/4 the size.
- The up to 98% cost reduction is modeled from the derived TPC-H SF100 benchmark (Sail 0.7.0 vs Spark 4.2.0): 1/10 the runtime times 1/4 the instance size is 1/40 the cost, assuming memory is the dominant instance sizing and pricing factor. It is a benchmark-derived model, not a guarantee for all workloads. The 40x more data at the same cost figure is the inverse of the same model.
- Sail ran with the optimizer.enable_join_reorder option turned on; the Sail configuration marks this option experimental.
- Benchmark data was generated with tpchgen-cli; the 2024 run used dbgen plus Parquet conversion.
- Cost is proportional to compute time. LakeSail's stateless workers scale to zero between jobs; Apache Spark clusters typically remain running between jobs, adding idle cost not captured in raw query runtime.
- Engineering hours (typically 20–40% of total Spark cost) are not included in the compute estimate. That's additional savings not captured in the benchmark number.
- Raw data and runnable scripts live in the ClickHouse/ClickBench Sail entry on GitHub.
Building in public forces the kind of transparency and rigor it takes to keep quality high. We're already seeing measurable speedups in our early tests with Sail.
Ready to see your numbers?
Book 15, 30, or 45 minutes with a LakeSail engineer and see Sail running against your own Spark workloads.
Or put it under the guarantee: a guaranteed Spark migration comes back correct, faster, and cheaper, or you owe nothing for the engineering.