# How the Ledger is compiled

Ledger method, read 10 Nov 2026

**The short answer.** The Spark Accelerator Ledger lists every published benchmark found for the twelve options, with who ran it, what it ran on and what it cost. Each entry carries its source and a publication date. Entries run newest first, and no number is derived, averaged or estimated.

## What counts as a published benchmark

An entry is a result a named party has published on its own page, with a link: a dated blog post, a documentation page, a GitHub results page, a paper or a project homepage. A claim without a workload, such as a percentage on a pricing page, is listed as published and noted as having no method stated.

Customer quotes that name no baseline and no workload are not benchmarks. Where an option has no benchmark, none found on 2026-11-10 is the entry: Microsoft Fabric's native execution engine has none.

## Dates and order

Entries are ordered by publication date, newest first, using the date on the source page. Where only a month or a year is shown, that is what the entry carries. Entries whose pages show no date are marked Not stated and listed last.

## The vendor-run label

Each entry says who ran the test. An entry is labelled vendor-run when the party that ran it sells or maintains the option tested, or sells a product in the comparison. Apache projects are named as the project that ran the test. A cloud provider's post written with a vendor is labelled with both names.

## Why no numbers are derived

Every figure is quoted as published, in the units the publisher used. The Ledger does not convert tests onto a common scale, compute speedups from published times, or average results across sources, because the tests use different data sizes, hardware, Spark versions and baselines. Two entries can only be compared by reading their hardware and baseline fields.

## Sources

- Comet TPC-DS benchmark results: https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/contributor-guide/benchmark-results/tpc-ds.md (read 10 Nov 2026)
- AWS Big Data blog on GPU Spark with EMR on EKS: https://aws.amazon.com/blogs/big-data/gpu-accelerated-apache-spark-with-amazon-emr-and-nvidia-rtx-pro-4500-on-amazon-ec2-g7-instances-runs-up-to-3-7x-faster/ (read 10 Nov 2026)
- Flarion benchmarks page: https://www.flarion.io/benchmarks (read 10 Nov 2026)
- DualBird Iceberg compaction benchmark post: https://dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-lower-cost (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://sparkaccelerationcompare.com/ledger/method/
