Side by side, read 10 Nov 2026
Amazon EMR runtime for Apache Spark and Microsoft Fabric native execution engine: the published facts in the same rows
Amazon EMR runtime for Apache Spark profileMicrosoft Fabric native execution engine profile
The same rows for both
| Row | Amazon EMR runtime for Apache Spark | Microsoft Fabric native execution engine |
|---|---|---|
| Kind | AWS-tuned Spark runtime on EMR | Velox-based engine inside Fabric Spark |
| 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. | Per Microsoft's documentation, no code modifications are required, and the engine is enabled with an Acceleration tab toggle or spark.native.enabled. The engine works with Parquet, Delta and CSV, including data reached through OneLake shortcuts. |
| 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 engine runs only inside Microsoft Fabric on Azure and does not run on AWS EMR or EKS. Microsoft's page gives no number, workload or dataset for the speedup, and a benchmark method or scripts: none found on 2026-11-10. |
| 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 page says the engine significantly raises query performance while minimizing operational costs, but gives no number, workload or dataset. 'Actual results vary by workload characteristics and configuration.' |
| 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. | Fabric is billed by capacity units (F2 to F4096 SKUs), pay-as-you-go or reservation. An opt-in Autoscale Billing for Spark runs Spark jobs on dedicated serverless resources at standard regional pay-as-you-go CU-hour rates, with a base Fabric capacity still required. SKU prices on the page load dynamically and were not readable. |
| 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). | Docs say no code modifications are required and no vendor lock-in. Unsupported operators fall back to JVM Spark. Listed limitations include decimal-to-float casting, timezone, round(), map() duplicate-key and collect_list ordering differences on Runtime 1.3, said to be resolved in Runtime 2.0. |
| 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. | Enable via the Acceleration tab toggle in an environment, or set spark.native.enabled to true at the start of a notebook or Spark job definition. Per-query disable is by setting the flag to false and re-enabling in later cells. Fabric Spark Advisor alerts show fallback. |
| 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. | Supports Runtime 1.3 (Spark 3.5, Delta Lake 3.2) and Runtime 2.0 (Spark 4.1, Delta Lake 4.1). Works with Parquet, Delta and CSV, including data reached via OneLake shortcuts. Not an AWS service. |
| 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. | Runs only inside Microsoft Fabric (Azure) on OneLake data. It does not run on AWS EMR or EKS. |
| 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. | No benchmark method, data or scripts are published for the engine's speedup on the documentation page. |
| 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 modifications stated. Microsoft's documentation says no code modifications are required. Unsupported operators fall back to JVM Spark. |
| 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. | Toggle in environment or Spark config. Enable it with the Acceleration tab toggle in an environment, or set spark.native.enabled to true in a notebook or Spark job definition. It needs Runtime 1.3 or 2.0. |
| 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. | Microsoft Fabric on Azure only. The engine runs only inside Microsoft Fabric on OneLake data, and does not run on AWS EMR or EKS. |
| 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. | Fabric capacity required. Fabric is billed by capacity units (F2 to F4096 SKUs), pay-as-you-go or reservation. Autoscale Billing for Spark still requires a base Fabric capacity. SKU prices were not readable on the page. |
| Ledger entries | EMR runtime claim on the AWS features page (run by its maker) | None found on 10 Nov 2026. |
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
- Microsoft Fabric Spark native execution engine: learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engin, read 10 Nov 2026
- Microsoft Fabric Spark native execution engine: azure.microsoft.com/en-us/pricing/details/microsoft-fabric, read 10 Nov 2026
Last reviewed 10 Nov 2026.