Side by side, read 10 Nov 2026
Amazon EMR runtime for Apache Spark and Speedata: the published facts in the same rows
Amazon EMR runtime for Apache Spark profileSpeedata profile
The same rows for both
| Row | Amazon EMR runtime for Apache Spark | Speedata |
|---|---|---|
| Kind | AWS-tuned Spark runtime on EMR | PCIe analytics chip plus Dash Spark plugin |
| Does well | AWS describes the runtime as 100% API compatible with open source Spark, so Spark jobs need no code changes. AWS publishes aws-samples/emr-spark-benchmark, a TPC-DS harness for a 3 TB Parquet dataset with steps for OSS Spark, EMR on EC2 and EMR Serverless. | Dash plugs into the Spark Catalyst optimizer, and per Speedata it delegates SQL elements it cannot accelerate, such as UDFs, to the CPU. Speedata offers a free Workload Analyzer that takes Spark logs and predicts per-query acceleration before purchase. |
| Limited | The runtime is proprietary to AWS and available only where EMR, EMR on EKS and EMR Serverless are, so jobs on other Spark hosts must migrate first. AWS's up to 4.5x figure names no TPC-DS scale or cluster, and the benchmark repository gives commands and configs but no results. | The APU is a PCIe card, so it needs physical servers; Speedata Acceleration for AWS runs the work in a Speedata-hosted environment, not in the customer's own EC2 fleet. No price list is published, and EMR, EKS, Databricks and table format support are not stated on the pages read. |
| Published speed results | AWS says the performance-optimized runtime executes up to 4.5x faster than open-source equivalents while delivering 2.7x faster Iceberg write performance. The page does not state the TPC-DS scale or cluster for these figures. | The home page claims the APU accelerates Apache Spark, batch ETL and AI data preparation up to 100x, with up to 90% lower TCO and zero code changes. Customer-result tiles show 62.7x acceleration on production Spark workloads (37 servers consolidated to 3), 90 to 8 hours of processing time on the same hardware budget, and 52x more performance per dollar than a GPU on analytics queries on an 'industry-standard benchmark'. No customer names, data sizes or method are given for these tiles. Speedata's blog says Microsoft's SIGMOD 2026 industry paper award 'CoddSpeed: Hardware Accelerated Query Processing in Microsoft Fabric' benchmarked the Speedata C-200 APU as one of three coprocessors. Per Speedata's summary of Table 2, standalone APU speedups on TPC-H SF100 (Parquet, warm in CPU memory) versus single-core SQL Server on an Intel Xeon Platinum 8473C were: Q07 36.7x, Q10 40.7x, Q12 49.4x, Q13 259.2x, Q16 61.5x. This is a selection of five queries, run against SQL Server on one core, not against Spark. The paper page on microsoft.com could not be fetched, so these numbers come from Speedata's blog only. The product page shows an example Workload Analyzer result of a query going from 4 minutes 3 seconds to 13.0 seconds (20X). It is presented as an illustration of the tool, with no workload details. |
| Published cost results and prices | EMR on EC2 price is added to the EC2 and EBS price. EMR on EKS is charged per vCPU-hour and GB-hour requested, from image download until pod end, rounded to the second, with a one-minute minimum, plus EKS and EC2 or Fargate cost. EMR Serverless is also available. Exact rates are region-specific and loaded by script on the page. | No price list is published. The pages offer buying a server or going through OEM or cloud partners. The only cost claims are up to 90% lower TCO, 37 servers replaced by 3, and 52x performance per dollar versus a GPU. Hardware must be bought or rented, so a comparison with pay-per-use cloud plugins needs a quote. |
| Code changes | Runtime is described as 100% API compatible with open source Spark, so Spark jobs need no code changes, but jobs must run on EMR (a migration if currently on other Spark hosts). | Dash software plugs into the Spark Catalyst optimizer, identifies compute-intensive work and offloads it to the APU. SQL elements that cannot be accelerated, such as UDFs, are delegated to the CPU while the rest of the query runs on the APU. The page shows enabling it with a jar and two settings: spark.plugins=com.speedata.spark.DashPlugin and spark.speedata.apus=1. |
| Tuning | The EMR docs list optimizations such as adaptive query execution, dynamic partition pruning, Bloom filter join and optimized join reorder. AQE-related features are on by default; some can be tuned with Spark properties. | The pages say zero code changes and a transparent plug-in. No per-job tuning guide or list of required Spark settings beyond the plugin class and spark.speedata.apus is published on the pages read. A free Workload Analyzer (upload Spark logs, run a CLI locally, or compare against TPC-DS) predicts per-query acceleration before purchase. |
| Spark versions, platforms and table formats | EMR supports Apache Iceberg v3 and Spark 4.0 per the features page, and runs on EMR on EC2, EMR on EKS and EMR Serverless. | The technology page says Dash accelerates Apache Spark 3.x workloads on Kubernetes, YARN and standalone cluster managers. The example command uses speedata-dash-0.8.1-spark_2.12.jar, and the company GitHub org has a container image repo built on Spark 3.5.2. The scope described is Spark SQL, DataFrame and batch ETL. EMR, EKS, Databricks, Iceberg, Delta and Hudi support are not stated on the pages read. Spark 4 is not mentioned. |
| Where it runs | AWS only. EMR runtime is available where EMR, EMR on EKS and EMR Serverless are available, and EMR on AWS Outposts is mentioned on the pricing page. | The APU is a PCIe Gen 5 card (C200 with the Callisto ASIC), so it needs physical servers. Options on the home page: a pre-configured 2U server with two C200 cards from Speedata; servers from OEM partners Dell and HPE; and 'Speedata Acceleration for AWS', where the customer keeps data in S3, syncs deltas to a Speedata-hosted environment, runs the work on the APU there and pushes results back. That means Speedata does not run inside the customer's own EC2 fleet. A European sovereign-cloud partner, Nebul, was announced on Feb 19, 2026. |
| How open its benchmarks are | AWS publishes aws-samples/emr-spark-benchmark with steps to run TPC-DS on OSS Spark (EC2 via Flintrock), EMR on EC2, EMR Serverless and a link to EMR on EKS. It uses a 3 TB TPC-DS Parquet dataset in a public S3 bucket, 3 iterations, and 104 queries with a pre-built spark-benchmark-assembly-3.3.0.jar. The repo gives commands and configs; it does not state results. The repo README notes that on OSS Spark query q95 did not complete, so it was rerun alone and merged, and says this was not an issue on EMR. This shows the OSS baseline needed manual handling. A companion repo aws-samples/emr-on-eks-benchmark has the EMR on EKS TPC-DS benchmark with 3 TB examples and notes scale factor and executor config must change for 100 GB or 1 TB. | The vendor's customer-result tiles have no published method. The GitHub org Speedata-io has five repositories, including a TPC-H data and query generator and a Spark 3.5.2 container image, but no repo with the benchmark results or APU software. A technical white paper is behind a form and was not read. |
| Change Budget: code | No code change stated. AWS describes the runtime as 100% API compatible with open source Spark, so Spark jobs need no code changes. | No code change stated. Speedata says zero code changes. The Dash plugin identifies compute-intensive work and offloads it, delegating UDFs to the CPU. |
| Change Budget: cluster | Run the jobs on an EMR release. Jobs must run on EMR (EC2, EKS or Serverless); a team on other Spark hosts migrates first. AQE-related features are on by default, and some can be tuned with Spark properties. | PCIe C200 card in each server. The APU is a PCIe Gen 5 card (C200 with the Callisto ASIC), so it needs physical servers. Enabling it uses a jar and two settings: spark.plugins=com.speedata.spark.DashPlugin and spark.speedata.apus=1. |
| Change Budget: cloud | AWS only. AWS lists the runtime where EMR, EMR on EKS and EMR Serverless are available, and mentions EMR on AWS Outposts. | On-premises, OEM or hosted AWS. Options are a 2U server with two C200 cards, OEM servers from Dell and HPE, or Speedata Acceleration for AWS, which runs the work in a Speedata-hosted environment and syncs data from S3. |
| Change Budget: vendor | EMR charges added to EC2 and EBS. The EMR price is added to the EC2 and EBS price. EMR on EKS is charged per vCPU-hour and GB-hour requested, plus EKS and EC2 or Fargate cost. | Speedata purchase; no price list. No price list is published. The pages offer buying a server or going through OEM or cloud partners. |
| Ledger entries | EMR runtime claim on the AWS features page (run by its maker) | Speedata APU on TPC-H SF100, Microsoft CoddSpeed paper (run by Microsoft (paper); numbers read from Speedata's blog); Speedata production Spark workload tile (run by its maker) |
How to read this page
The rows hold what each vendor or a named third party published, with no conclusion drawn. Benchmarks in the two columns were run on different hardware, data and baselines unless the Ledger entry says otherwise, so the numbers are not comparable across columns. The Ledger method explains how entries are recorded.
Sources
- Amazon EMR runtime for Apache Spark: aws.amazon.com/emr/features/spark, read 10 Nov 2026
- Amazon EMR runtime for Apache Spark: github.com/aws-samples/emr-spark-benchmark, read 10 Nov 2026
- Amazon EMR runtime for Apache Spark: github.com/aws-samples/emr-on-eks-benchmark, read 10 Nov 2026
- Amazon EMR runtime for Apache Spark: aws.amazon.com/emr/pricing, read 10 Nov 2026
- Amazon EMR runtime for Apache Spark: docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-spark-performance.html, read 10 Nov 2026
- Speedata: speedata.io, read 10 Nov 2026
- Speedata: speedata.io/post/259-faster-what-microsoft-s-award-winning-sigmod-paper-, read 10 Nov 2026
- Speedata: speedata.io/product, read 10 Nov 2026
- Speedata: speedata.io/technology, read 10 Nov 2026
- Speedata: speedata.io/workload-analyzer, read 10 Nov 2026
- Speedata: github.com/Speedata-io, read 10 Nov 2026
Last reviewed 10 Nov 2026.