Benchmarks · /benchmarks
10.4× faster than Spark, on one machine.
The same 22 TPC-H-derived queries, the same Parquet files, the same laptop. Every number below comes with its method, and you can rerun all of it with the open harness.
Derived from TPC-H, not an audited TPC-H result. Gate runs of 2026-11-12/13 on Krishiv commit f345c5e, approved for the 0.2 release.
Per query, derived from TPC-H, SF100, cold (build of 2026-11-10; the gate build is faster)
log scale · lower is better · ratio = Spark / KrishivSF1000: can it finish?
At 1 TB, Krishiv completes all 22 queries inside its 20 GB memory limit by spilling to disk. Spark, on the same machine and limit, finished 6 of the 17 queries it ran within the 30-minute cap per query.
All 22 SF1000 queries complete, the slowest (Q18) in 654 s. DuckDB runs out of memory on Q01 (a run needing 35 GB) and Q18 at 28 GB; those two were run alone without a cgroup cap. The SF1000 geomean (1.26×) covers the 21 queries with a DuckDB time. Peak resident memory: Krishiv 23.5 GiB (Q09), DuckDB 22.0 GiB (Q21), both above the 20 GB engine limit but inside the 28 GB container.
Method
| Machine | One laptop (i7-9750H, 12 threads, 64 GB RAM, NVMe SSD, Linux, powersave CPU governor) |
|---|---|
| Data | Derived from TPC-H, not audited: Parquet generated with tpchgen 3.0.0 (not dbgen), SF10, SF100 and SF1000, read in place (no loading step) |
| Runs | Cold: dataset evicted from the OS page cache before every run; two cold runs per query, sequential, one engine after another |
| Limits | 12 threads and a 20 GB engine memory limit for Krishiv and DuckDB, inside a 28 GB cgroup; Spark driver memory 20g. Peak RSS can exceed the engine limit (Krishiv 23.5 GiB, DuckDB 22.0 GiB). |
| Versions | Krishiv 0.2 (commit f345c5e) · Apache Spark 4.2.0, local[*] over Spark Connect, spark.sql.shuffle.partitions=24, Spark 4 defaults otherwise (a run with 12 partitions was slower) · DuckDB 2.0.0 |
| Correctness | Krishiv's results match DuckDB 2.0.0 on tpchgen data (row count and checksum): 22 of 22 at SF10 and SF100; at SF1000 20 of 22 against a fresh DuckDB run, Q01 against an earlier DuckDB run, Q18 consistent across repeated Krishiv runs only. Spark's answers were not verified; Spark times include the Connect round trip. |
| TPC notice | Derived from the TPC-H benchmark. These are not TPC-H results: they are unaudited and not comparable with published TPC results. TPC-H is a trademark of the Transaction Processing Performance Council. |
Reproduce it
git clone https://github.com/KrishivAI/krishiv-engine cd krishiv-engine/bench uv run krishiv-bench reproduce --suite tpch --sf 100
Full harness and engine configurations are in the repository.
★ Star on GitHubDistributed
Coming in a later release. It will measure: Scale-out, derived from TPC-H, across a cluster: speed-up per added worker and shuffle cost.
Lakehouse
Coming in a later release. It will measure: Reads and writes on Iceberg and Delta tables: scan pruning, commit time and compaction.
Streaming
Coming in a later release. It will measure: Event throughput and end-to-end latency on Nexmark-style queries, with and without checkpoints.
Apache Spark and Spark are trademarks of the Apache Software Foundation. DuckDB is a trademark of the DuckDB Foundation.