{
 "name": "Option facts",
 "edition": "2026-11-10",
 "read_date": "2026-11-10",
 "source": "https://sparkaccelerationcompare.com/datasets/",
 "license": "CC BY 4.0",
 "cite": "Spark Acceleration Compare, \"Spark Accelerator Ledger\" and \"Change Budget\", edition 10 Nov 2026, https://sparkaccelerationcompare.com/datasets/ (CC BY 4.0).",
 "description": "Every published fact behind the option profiles, with its topic, source URL and read date. Alphabetical by option.",
 "rows": [
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "speed",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://aws.amazon.com/emr/features/spark/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "open",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://github.com/aws-samples/emr-spark-benchmark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "open",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://github.com/aws-samples/emr-spark-benchmark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "open",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://github.com/aws-samples/emr-on-eks-benchmark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "cost",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://aws.amazon.com/emr/pricing/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "rewrite",
   "fact": "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).",
   "source_type": "vendor-docs",
   "source_url": "https://aws.amazon.com/emr/features/spark/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "tune",
   "fact": "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.",
   "source_type": "cloud-provider-docs",
   "source_url": "https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-spark-performance.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "stack",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://aws.amazon.com/emr/features/spark/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "where",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://aws.amazon.com/emr/pricing/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Amazon EMR runtime for Apache Spark",
   "topic": "breadth",
   "fact": "The runtime is proprietary to AWS and is a tuned build of Apache Spark, not a native C++ replacement. The benchmark harness is open sample code on GitHub.",
   "source_type": "vendor",
   "source_url": "https://github.com/aws-samples/emr-spark-benchmark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "speed",
   "fact": "The project says it has passed all TPC-DS and TPC-H cases and, compared with Spark 3.5, runs about 2x faster and saves about 50% of cluster resources. The only published detail is the TPC-DS 1 TB benchmark page; no per-query numbers are in text form (results are a chart).",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "rewrite",
   "fact": "Auron is added by putting a jar on the Spark classpath and setting spark.auron.enable, the AuronSparkSessionExtension and the AuronShuffleManager; no job changes. The project describes fine-grained fallback for unsupported operators, and the Spark UI has an Auron tab that records per-operator fallback reasons. You must build the jar yourself (Rust nightly and JDK required); the getting-started page describes building from source.",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "tune",
   "fact": "The suggested config disables Spark off-heap memory and moves memory into executor overhead (4096 MB in the quick start). The benchmark used executor memory 8g with overhead 16384 for Auron versus 20g with 4096 for plain Spark, plus spark.auron.memoryFraction 0.8, forceShuffledHashJoin and sort-merge-join and UDAF fallback settings. ORC with large string/binary values needs spark.auron.orc.batchSize lowered.",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/documents/benchmarks.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "stack",
   "fact": "The build script lists supported Spark versions 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1 and 4.2 with Scala 2.12 and 2.13, and Celeborn 0.5/0.6 and Uniffle 0.10 remote shuffle. The 8.0.0 notes add Spark 4.0 and 4.1 build support. No EMR, EKS or Databricks support is documented.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/auron/master/auron-build.sh",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "stack",
   "fact": "The 8.0.0-incubating release notes say it added and expanded native scan support for Apache Iceberg, Apache Hudi and Apache Paimon, including Copy-on-Write tables and Iceberg changelog scans. The homepage says it supports Hudi and Paimon. 8.0.0 also adds Flink integration. Delta Lake is not mentioned in the fetched pages.",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/archives/v8.0.0-incubating.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "where",
   "fact": "Build needs Rust nightly and JDK; the README says regularly tested on JDK 8, 11 and 17 and also on JDK 21. The build script supports OS images centos7, ubuntu24, rockylinux8, debian11 and azurelinux3, and macOS builds were added in 8.0.0. The homepage says it supports storage such as HDFS and S3. No cloud-specific instance guidance was found.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/auron/master/README.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "open",
   "fact": "The benchmark page publishes the method end to end: TPC-DS 1 TB data generated with a datagen tool (derived from maropu/spark-tpcds-datagen) and run with a benchmark runner (derived from databricks/spark-sql-perf), both in the auron-project/tpcds-tools repo, with the full Spark config. It ran Spark 3.5.6 against Auron 6.0.0-preview on YARN. Node types and counts are not given (the config shows executor cores 8 and a very large maxExecutors).",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/documents/benchmarks.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "breadth",
   "fact": "Apache-2.0 licensed under the Apache Software Foundation; GitHub repo (originally kwai/blaze) created 2021-06-28, about 1,800 stars. The homepage says it is verified in production with exabytes of data; that claim names no company.",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Auron (incubating), formerly Blaze",
   "topic": "profile",
   "fact": "Releases: 8.0.0-incubating (2026-07-18), 7.0.0-incubating (2026-03-04), 6.0.0-incubating (2025-10-17), 5.0.0 (2025-04-28), 4.0.1 (2024-12-10), 4.0.0 (2024-10-10), going back to 2.0.6 in Sep 2023 under the Blaze name.",
   "source_type": "open-source-project",
   "source_url": "https://auron.apache.org/archives/all-releases.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "speed",
   "fact": "On an EKS cluster (r6i instances, EBS storage, data in S3), TPC-DS derived queries at scale factor 1000 (103 queries, zstd Parquet, each query run twice and the mean reported) took 994 s on Spark 4.2.0, 601 s on Comet 1.1.0 and 488 s on Comet 1.2.0. The page says Comet 1.2.0 is 2.0x faster than Spark and 1.2x faster than Comet 1.1.0.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/contributor-guide/benchmark-results/tpc-ds.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "speed",
   "fact": "The same tables and settings on Spark 4.1.3: Spark 1,336 s, Comet 1.1.0 613 s (2.18x), Comet 1.2.0 532 s (2.51x). The project explains that Spark 4.1.3 is slower than 4.2.0 on this cluster mostly because of the default S3A input stream (classic vs S3 Analytics Accelerator), so the speedup depends on the Spark baseline; Spark 4.2.0 with the classic stream took 1,294 s.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/contributor-guide/benchmark-results/tpc-ds.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "rewrite",
   "fact": "Comet is enabled with spark.plugins, a shuffle manager and off-heap settings, with no job code changes. Unsupported operators and expressions fall back to Spark; the plan explain output marks fallback reasons with [COMET: ...]. Some expressions have native implementations that differ from Spark and are off unless a user sets allowIncompatible; Iceberg writes are off by default.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/user-guide/latest/compatibility/index.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "tune",
   "fact": "The tuning guide says every deployment must configure how much memory Comet can use (off-heap pool and executor memory overhead), and has further pages for shuffle, Parquet and Iceberg scans, operators, and reducing row/columnar conversions. The benchmark config used spark.memory.offHeap.size=32G and spark.comet.exec.memoryPool.fraction=0.8 alongside 64G executor memory and 10G overhead.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/user-guide/latest/tuning.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "stack",
   "fact": "Comet supports Spark 3.5.9 (Scala 2.12/2.13), 4.0.4, 4.1.3 and 4.2.0 with JDK 17 or later (JDK 11 dropped in 1.1.0). The docs warn it may not fully work with cloud-provider Spark forks, so EMR, Databricks and similar managed runtimes are not documented as supported.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/user-guide/latest/installation.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "stack",
   "fact": "Comet accelerates Iceberg tables with Parquet data files: a native Iceberg reader (on by default, tested with Iceberg 1.5, 1.8, 1.9, 1.10 and 1.11) and native writes (off by default via spark.comet.write.iceberg.enabled). Delta Lake support is marked experimental. The docs list known issues where results differ from Spark. Remote shuffle via Celeborn is supported.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/user-guide/latest/iceberg.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "where",
   "fact": "Published Maven Central jars bundle native libraries for Linux on amd64 and arm64 only; Apple Silicon macOS must build from source. Nightly snapshot jars are not Apache releases. The EKS benchmark ran on r6i instances; the EC2 guide recommends a c7i.4xlarge for single-node runs. No GPU or special hardware is required.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/datafusion-comet/main/docs/source/user-guide/latest/installation.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "open",
   "fact": "The project publishes benchmark scripts in benchmarks/tpc, data generation in the apache/datafusion-benchmarks repo, step-by-step guides for macOS, AWS EC2 (single node) and spark-sql-perf, and the full list of non-default Spark settings used for the TPC-DS run (executors 32 x 16 cores, 64G memory, shuffle partitions 512, S3A settings). Node count and instance size of the EKS cluster beyond the r6i family are not stated on the results page.",
   "source_type": "open-source-project",
   "source_url": "https://datafusion.apache.org/comet/contributor-guide/benchmarking.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "breadth",
   "fact": "Licensed Apache-2.0 under the Apache Software Foundation; the docs site footer shows copyright 2023 to 2026 Apache Software Foundation. GitHub repo created 2024-01-15, about 1,300 stars.",
   "source_type": "open-source-project",
   "source_url": "https://api.github.com/repos/apache/datafusion-comet",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache DataFusion Comet",
   "topic": "profile",
   "fact": "GitHub releases: 1.0.0 (2026-08-07), 1.1.0 (2026-10-06), 1.2.0 (2026-11-03), roughly monthly after 1.0.",
   "source_type": "open-source-project",
   "source_url": "https://api.github.com/repos/apache/datafusion-comet/releases?per_page=3",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "speed",
   "fact": "The project homepage reports TPC-H and TPC-DS at 3 TB on Intel Xeon Platinum 8592+ with Spark 3.3.1: overall 3.34x on TPC-H (up to 23.45x on single queries) and 3.02x on TPC-DS (up to 13.75x on single queries). The page does not link a method or scripts for these numbers; the hardware is from Intel, a contributor.",
   "source_type": "open-source-project",
   "source_url": "https://gluten.apache.org/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "rewrite",
   "fact": "Gluten is a Spark plugin that needs no DataFrame or SQL changes, only configuration: spark.plugins=org.apache.gluten.GlutenPlugin, off-heap memory enabled with a size, ColumnarShuffleManager and the bundle jar.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/docs/get-started/getting-started.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "rewrite",
   "fact": "Unsupported operators fall back to vanilla Spark through columnar-to-row and row-to-columnar conversions. The Velox backend limitations page lists known fallbacks and differences: ANSI mode always falls back, case-sensitive mode may give wrong results, regexp functions use RE2 (no lookaround), file scans fully support only Parquet and partly ORC, partitioned scans need partition info in the path, and JSON functions differ for single-quoted strings.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/docs/backends/velox/velox-backend-limitations.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "tune",
   "fact": "Off-heap memory must be enabled and sized (the quick start uses spark.memory.offHeap.size=20g and says to adjust it for the environment), and the columnar shuffle manager is needed for native shuffle. Docs also describe a troubleshooting page, Celeborn and Uniffle remote shuffle settings, and a setting (spark.gluten.sql.fallbackRegexpExpressions) for users who cannot tolerate regexp differences. Binary jars must load ahead of Spark's jars because Gluten overrides some Spark classes.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/docs/get-started/getting-started.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "stack",
   "fact": "The docs state officially supported Spark versions are 3.4.4, 3.5.5, 4.0.2 and 4.1.1 (Spark 4.x needs JDK 17+ and Scala 2.13). The downloads page still lists Spark 3.3 binaries for 1.6.0 and 1.7.0, and the homepage benchmark used Spark 3.3.1. Using an unofficial Spark version can throw NoSuchMethodError at runtime. Docs do not mention EMR, EKS or Databricks support.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/docs/backends/velox/get-started/Velox.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "stack",
   "fact": "Velox backend docs: Iceberg reads of copy-on-write and merge-on-read tables are supported but the Iceberg page says only reading is supported and only Spark 3.4 is well tested; Hudi supports reading COW tables only; Paimon supports non-primary-key tables only; Delta has a build profile and a doc page. Celeborn 0.3 to 0.5 and Uniffle 0.9.2 remote shuffle are supported.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/docs/backends/velox/get-started/VeloxIceberg.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "where",
   "fact": "Official build and test platform is Ubuntu 20.04/22.04 or CentOS 8; the downloads page says binaries were built on CentOS 7 with static linking on Intel Xeon Platinum 8272CL class CPUs, and that performance and compatibility are not guaranteed on other OSes or hardware, so building from source is recommended. Docs have pages for S3, GCS and ABFS storage.",
   "source_type": "open-source-project",
   "source_url": "https://gluten.apache.org/downloads/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "open",
   "fact": "The repo includes the gluten-it integration test and benchmark tool (data generation, query runs, result comparison against a baseline) for building and running TPC-style queries locally, supported on Spark 3.4, 3.5, 4.0 and 4.1 profiles. The homepage TPC-H and TPC-DS numbers do not themselves link to a run configuration.",
   "source_type": "open-source-project",
   "source_url": "https://raw.githubusercontent.com/apache/gluten/main/tools/gluten-it/README.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "breadth",
   "fact": "The Powered By page lists adopters including Alibaba, Baidu, Bytedance, BIGO, IBM, Kyligence, Meituan, Microsoft (Fabric), Google (Lightning engine), Netease, Oracle (OCI), Palantir, Pinterest, SF Express and Tencent. These are self-reported entries. The homepage benchmark runs on Intel hardware; the docs describe Velox as Meta's C++ execution library. Project license is Apache-2.0 (GitHub API).",
   "source_type": "open-source-project",
   "source_url": "https://gluten.apache.org/poweredby/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Apache Gluten with the Velox backend",
   "topic": "profile",
   "fact": "GitHub releases: v1.7.0 published 2026-08-26 (rc1 2026-08-17). The downloads page lists 1.7.0 as 'Jun. 6 2025', which conflicts with the GitHub date and looks like a typo; 1.6.0 is listed as Mar. 10 2026 and 1.5.0 as Oct. 29 2025. Repo created 2021-12-06, about 1,600 stars.",
   "source_type": "open-source-project",
   "source_url": "https://api.github.com/repos/apache/incubator-gluten/releases?per_page=3",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "profile",
   "fact": "Photon is the Databricks-native vectorized query engine. It replaces the JVM Spark SQL execution layer with a C++ runtime for supported operations while Catalyst still plans the query.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "where",
   "fact": "Photon is documented only as part of Databricks compute on AWS, Azure and GCP (cloud tabs on the page). It is not offered as a standalone engine for open source Spark, EMR or other platforms in the docs read.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "rewrite",
   "fact": "Docs say Photon works with existing Spark API code with no changes. Unsupported operations fall back transparently to the Spark runtime for the remainder of that operation. Photon does not support UDFs, RDD APIs or Dataset APIs, and stateful streaming is not supported.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "tune",
   "fact": "Photon is on by default for classic all-purpose, jobs compute and classic pipelines (checkbox Use Photon Acceleration), and enabled on serverless and SQL warehouses. If you use the Clusters or Jobs API you must set runtime_engine to PHOTON. Queries under about two seconds see no meaningful gain. Users check the Spark UI to see fallback.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "stack",
   "fact": "Photon accelerates Delta Lake, Apache Iceberg and Parquet writes, supports SQL and DataFrame APIs in Python, R, Scala and Java, and stateless streaming from Delta, Parquet, CSV, JSON, Kafka and Kinesis. It runs on Databricks Runtime, so the Spark version is the Databricks Runtime version, not a user choice of open source Spark.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "where",
   "fact": "Photon supports a set of driver and worker instance types including Graviton. Graviton with Photon does not support Databricks Container Services for dedicated compute or SQL warehouses.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "cost",
   "fact": "Photon instance types consume DBUs at a different rate than the same instance without Photon, so cost depends on the DBU multiplier on the pricing page, not only on speedup. Databricks defines a DBU as a normalized unit of processing power used for pricing.",
   "source_type": "vendor-docs",
   "source_url": "https://www.databricks.com/product/pricing",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "speed",
   "fact": "Docs claim up to 5x better price/performance for data and analytics workloads compared to other cloud data warehouses, as measured by industry-standard TPC-DS benchmarks. This compares against warehouses, not against open source Spark.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.databricks.com/en/compute/photon.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "speed",
   "fact": "The SIGMOD 2022 Photon paper reports customers observed average speedups of 3x over the previous Databricks Runtime and maximum speedups of over 10x. The baseline is Databricks' own prior Spark-based runtime, not open source Spark.",
   "source_type": "vendor",
   "source_url": "https://people.eecs.berkeley.edu/~matei/papers/2022/sigmod_photon.pdf",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "speed",
   "fact": "Databricks announced an audited 100TB TPC-DS record in November 2021: 32,941,245 QphDS versus 14,861,137 for the previous record holder (Alibaba). The post says Databricks SQL 'is not based on Apache Spark, but rather Photon'. The run was on Databricks SQL, not a Spark batch job.",
   "source_type": "vendor",
   "source_url": "https://www.databricks.com/blog/2021/11/02/databricks-sets-official-data-warehousing-performance-record.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "open",
   "fact": "The TPC-DS record is a TPC-audited result, so a full report exists under TPC rules, but it needs a Databricks SQL warehouse and is not a repeatable open script. No public repo for Photon speedups on user Spark jobs was found.",
   "source_type": "vendor",
   "source_url": "https://www.databricks.com/blog/2021/11/02/databricks-sets-official-data-warehousing-performance-record.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "Databricks Photon",
   "topic": "breadth",
   "fact": "Photon is proprietary to Databricks. It was described in a SIGMOD 2022 paper by Databricks engineers. Source code is not open.",
   "source_type": "vendor",
   "source_url": "https://people.eecs.berkeley.edu/~matei/papers/2022/sigmod_photon.pdf",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "speed",
   "fact": "The home page headline claims 10X faster at 80% cost reduction for GenAI and analytics data processing. The DPA-S page says it can reduce costs by up to 80% on qualifying workloads without rewriting applications or migrating data. No workload, baseline or method is attached to the 10X/80% figures.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "cost",
   "fact": "Named customer quotes on the vendor site: Akad Seguros (CTO) says costs fell by more than 50%; ShareChat (VP of Data) says the heavy OLAP cube jobs now complete on OSS Spark and costs fell by 50%; RevSure.ai (CEO) reports gains in days with zero application changes; McAfee and Samsung SDS America describe 'promising results' only. These are testimonials with no baseline, workload or method.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "cost",
   "fact": "The DPA-S page describes pay-as-you-go pricing billed through the AWS and GCP marketplaces ('Use more and Save more'). No price per unit is published on the pages read. The docs require a Subscription ID and license bucket path tied to registered AWS account IDs.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/dpa",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "rewrite",
   "fact": "DPA-S is presented as working with existing Spark clusters and jobs with no application rewrites or data migration; languages are PySpark, Scala and Spark SQL. Workloads to select: compute-intensive Parquet/ORC SQL and DataFrame jobs. Workloads to avoid: heavy use of RDDs and UDFs. The docs list limitations: native CPU acceleration is not used when ANSI mode is on (queries run on the JVM), case-sensitive mode is not supported and may return incorrect results, plus listed caveats for regexp functions, file source formats, JSON functions and NaN.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/dpa",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "tune",
   "fact": "Mandatory Spark settings in the EKS docs include spark.plugins=org.apache.gluten.GlutenPlugin, the subscription ID and license location env vars, spark.memory.offHeap.enabled=true with a positive spark.memory.offHeap.size, spark.shuffle.manager=org.apache.spark.shuffle.sort.ColumnarShuffleManager and netty Java options. CBO settings are recommended. The DPA-S page tells users to adjust Spark configuration (shuffle manager, memory tuning). So some per-deployment configuration is required, in contrast to 'no tuning' claims by other vendors.",
   "source_type": "vendor-docs",
   "source_url": "https://datapelago-docs.readthedocs-hosted.com/en/latest/deploy-on-aws.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "stack",
   "fact": "On AWS, DPA-S is available for OSS Spark on EKS as a Docker container in ECR: Spark 3.5.1, Java 11, Scala 2.12, Ubuntu 22. EMR and Databricks are not mentioned on the AWS docs page. The vendor page says 'multiple Spark versions on Google Cloud and AWS'. Lakehouse formats Iceberg, Hudi and Delta are named only in a reseller testimonial (Twingo) on the vendor site.",
   "source_type": "vendor-docs",
   "source_url": "https://datapelago-docs.readthedocs-hosted.com/en/latest/deploy-on-aws.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "stack",
   "fact": "GCP docs list supported combinations: Dataproc 2.2.49 with Spark 3.5.1, Dataproc 2.1.75 with Spark 3.3.2, OSS Spark 3.5.1 and OSS Spark 3.3.4 (all Java 11, Scala 2.12) and a GKE deployment. Docs version header is 3.1.7.",
   "source_type": "vendor-docs",
   "source_url": "https://datapelago-docs.readthedocs-hosted.com/en/latest/deploy-on-gcp.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "where",
   "fact": "Runs in the customer's own cloud account on AWS (EKS) and Google Cloud (Dataproc, GKE). The Nucleus engine targets CPU, GPU and FPGA. The Nucleus-versus-cuDF test used an AWS p5.48xlarge with H100 GPUs; the DPA-S docs pages read do not state a GPU requirement, so the hardware needed for DPA-S itself was not confirmed.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/technology",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "stack",
   "fact": "The technology page says the engine builds on Substrait-based open-source frameworks such as Apache Gluten and Velox; the docs configure the Gluten plugin class. The Gluten initiator is quoted on the home page in support. Nucleus and DPA-S themselves are proprietary and licensed.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "speed",
   "fact": "DataPelago's blog (Aug 21, 2025) compares Nucleus v3.0 with NVIDIA cuDF 25.04.00 on one H100 of an AWS p5.48xlarge, for single operators. Nucleus is up to 10.5x faster on project, up to 10.1x on filter, up to 4.3x on aggregate, up to 4.5x on hash aggregate, and up to 8.2x on Top-K. These are operator microbenchmarks against a GPU library, not end-to-end Spark jobs.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/resources/DataPelago-Nucleus-Vs-Nvidia-cuDF",
   "read_date": "2026-11-10"
  },
  {
   "option": "DataPelago",
   "topic": "profile",
   "fact": "Founder and CEO Rajan Goyal was previously CTO at Fungible. DataPelago, Inc. is at 100 View Street, Mountain View, CA. Timeline from the press page: Universal Data Processing Engine unveiled Oct 1, 2024; President John Chirapurath appointed Jul 28, 2025; DPA-S launched Aug 5, 2025; Nucleus-versus-cuDF release Aug 22, 2025; Fast Company Most Innovative Companies of 2026 (Mar 24, 2026); Data Breakthrough award (May 13, 2026). Investor/partner logos on the home page include Taiwania, Qualcomm, Eclipse, Alter and Nautilus (alt text); no round sizes were found.",
   "source_type": "vendor",
   "source_url": "https://www.datapelago.ai/press",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "The home page body text states the headline claim as 10x-30x faster data processing with 50%-90% lower costs and no changes required. The same wording appears in the page's JSON-LD organization description and in the April 28, 2026 blog post.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "The raw HTML of the home page has a different range in its meta description and og:description (and twitter:description): 10x-100x faster. This is the meta tag, not body text. The February 5, 2026 funding blog post also says 10-100x faster and 50-90% cost savings. The body text of the home and product pages says 10x-30x, so the two ranges differ by site location.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "The product page repeats the 10x-30x end-to-end figure labeled 'Instance for instance' and 50%-90% cost reduction labeled 'Workload for workload'. The meta description of the product page is only 'Plug-and-play Spark acceleration.'",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "stack",
   "fact": "The home page says the plugin is compatible with Apache Spark, Amazon EMR and Amazon EKS. It lists 'Optimized out of the box', 'Migration-free' and 'No more performance tuning and troubleshooting'. No Spark version numbers, Databricks support or Iceberg/Delta/Hudi support list are stated on the home, product, about or resources pages. Iceberg appears only in the compaction benchmark and in the meta description of the Dec 1, 2025 demo post ('Accelerate Apache Spark and Apache Iceberg').",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "rewrite",
   "fact": "Onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin. The page shows three steps: change instance type, use our Spark plugin, see the results. The about page says 'No infrastructure changes. No code changes.' The compaction blog says Spark still handles planning, scheduling and fault tolerance and no pipeline rewrite or platform migration is needed.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "rewrite",
   "fact": "A DualBird engineer states the FPGA path accelerates a defined set of operators (sort, join, aggregation and others). Workloads dominated by Python UDFs or unsupported operators fall back to CPU and do not see the same benefit yet. Coverage is described as expanding.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/resources/blog/a-simpler-spark",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "tune",
   "fact": "DualBird claims tens of Spark settings (executor sizing, CPU-memory ratios, parallelism) become irrelevant, disk spills effectively disappear and data skew stops causing spills, because only a few tasks run at once on the FPGA. The product page says the majority of common Spark performance configurations do not exist when using the solution. Cluster sizing reduces to the number of F2 nodes. These are vendor claims, not independently tested. Part 2 of the series (Sep 1, 2026) says skew still costs time, but less, and that it does not need repartitioning or salting.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "profile",
   "fact": "Use cases on the home page: AI data infrastructure (feature engineering and AI data prep), big data pipelines, and accelerating data analytics (fresher data for dashboards). The Iceberg compaction benchmark is the one worked example with published method.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "Home and product pages show a '110GB Enrichment Pipeline (JOIN Denormalization)' benchmark: 50%-85% lower EC2 cost with 6x-18x higher performance ceiling. The pages give no hardware, baseline, dates or method, and no link to a write-up was found.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "Sort-based Iceberg compaction on 100 GB, compared with vanilla Spark and with an unnamed 'C++ accelerated Spark' (unnamed) with tuned EBS, memory and parallelism at each cluster size. Dataset is synthetic: about 370 million rows, 64 mixed-type columns, ZSTD level 3. Results: roughly 12-20x faster single-task execution, 55-85% lower EC2 cost, stable cost across scaling, about 6x higher practical performance ceiling. Cost per terabyte compacted is stated as about $2/TB for DualBird versus about $6/TB rising past $13/TB for CPU clusters. Part of the saving is attributed to F2 local NVMe replacing EBS volumes. The home page shows 'X15-X20' single-task speedup for the same benchmark, while the June 11, 2026 blog and the white paper landing page say 12-20x. The two do not match.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-lower-cost",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "open",
   "fact": "The white paper (dated July 1, 2026) has a landing page that restates the results and says methodology, system architecture and detailed analysis are in a download. The full document is gated behind a form and was not readable. The blog gives dataset shape and baselines but not instance counts, Spark version, configs or scripts. No public repo was found (github.com/dualbird returns 404).",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "speed",
   "fact": "The 'Single Task Performance' home-page tile says X15-X20 speedup for the same cluster size while reducing cost by over 50%. The blog describes the single-task comparison as against vanilla Spark, and the April 28 post as against 'a high-end C++ columnar engine running on a single CPU core'. The baseline wording is therefore not consistent across pages.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "where",
   "fact": "DualBird needs AWS EC2 F2 instances. AWS describes F2 as second-generation FPGA instances with up to 8 AMD Virtex UltraScale+ HBM VU47P FPGAs, 16 GiB HBM per FPGA, 3rd-gen AMD EPYC (Milan) CPUs up to 192 vCPU, up to 2 TiB memory and up to 7.6 TiB NVMe. Sizes: f2.6xlarge (1 FPGA, 24 vCPU, 256 GiB), f2.12xlarge (2 FPGAs, 48 vCPU, 512 GiB), f2.48xlarge (8 FPGAs, 192 vCPU, 2,048 GiB).",
   "source_type": "cloud-provider-docs",
   "source_url": "https://aws.amazon.com/ec2/instance-types/f2/",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "where",
   "fact": "The AWS 'instance types by Region' doc lists F2 in eight regions: us-east-1 (N. Virginia), us-west-2 (Oregon), ap-northeast-1 (Tokyo), ap-northeast-2 (Seoul), ap-southeast-2 (Sydney), ca-central-1 (Canada Central), eu-central-1 (Frankfurt) and eu-west-2 (London). F2 is not listed in other regions on that page (for example us-east-2, eu-west-1). DualBird is AWS-only: no other cloud is mentioned.",
   "source_type": "cloud-provider-docs",
   "source_url": "https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "where",
   "fact": "The product page says deployment runs on the customer's own servers in their AWS environment and 'Everything stays under your control'.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "breadth",
   "fact": "DualBird's own blog (Feb 5, 2026) announces a $25M raise led by Lightspeed Venture Partners with Angular Ventures, Uncork Capital and Bessemer Venture Partners. It says general availability was planned for early 2026 and that early deployments with design partners showed hours-to-minutes gains. The funding is confirmed by the company itself only. Lightspeed's page returned HTTP 403 and no press article was reachable.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/resources/blog/dualbird-raises-25m",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "profile",
   "fact": "About page: founded and led by semiconductor and distributed data systems veterans; positions FPGA-based acceleration as a drop-in Spark plugin on standard AWS instances. Blog posts date from Dec 1, 2025 to Sep 1, 2026. Footer copyright reads 2025. Contact: contact@dualbird.io.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/about",
   "read_date": "2026-11-10"
  },
  {
   "option": "DualBird",
   "topic": "cost",
   "fact": "No pricing, price list or marketplace listing was found on the site. Cost claims are only percentages (50%-90% lower, 55%-85% lower EC2) and the about $2/TB versus $6-13/TB compaction figure. The pricing model for the plugin itself is not stated, so users cannot tell whether F2 instance price or license fee is included in the claimed savings.",
   "source_type": "vendor",
   "source_url": "https://dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-lower-cost",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "speed",
   "fact": "The home page headline is 'Run faster, spend less, scale further, without changing a line of code', with tiles for 6 minute setup, 3x performance gains and 60% cost reduction. The tiles carry no workload or method on the page.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "speed",
   "fact": "The benchmarks page (September 2026) compares six engines on TPC-DS (103 queries) on one i4i.8xlarge reading Parquet from S3. Flarion is faster than vanilla Spark, Comet and Gluten, and slower than Databricks Photon in both scales. At 100 GB: Spark 1,135 s, Flarion 386 s, Photon 362 s. At 1 TB: Spark 135.6 min, Flarion 38.3 min, Photon 30.4 min. The page labels these as benchmark figures, not customer results, and not an audited TPC result.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/benchmarks",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "open",
   "fact": "The benchmark page publishes the machine, Spark 3.5.5 baseline, engine builds (Comet 1.0.0, Gluten 1.7.0 Velox, Databricks DBR 16.4 LTS), memory budgets, shuffle partitions (64), AQE on, no statistics/CBO, per-query caps (600 s at 100 GB, 1,800 s at 1 TB) and lower of two runs at 100 GB and one run at 1 TB. It discloses that q72 is counted at vanilla Spark's time for Gluten and Comet. It says the open-source engines can be rerun from public releases, but Flarion itself is not downloadable ('contact us'), and no repo or scripts were found.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/benchmarks",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "cost",
   "fact": "Usage-based list prices: self-hosted Spark on AWS, Azure or GCP $0.009 per CPU hour; fully managed Spark (EMR, GCP managed Spark, Azure HDInsight) $0.012 per CPU hour; Databricks $0.095 per DBU; on-premises $0.75 per CPU per month. Billing is on accelerated Spark cores (driver plus executors). A free assessment simulates each job from logs and reports projected runtime and compute.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/pricing",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "rewrite",
   "fact": "Flarion is one JAR inside the existing cluster, with no agents or separate services. UDFs and UDAFs run on Spark as before. Operations Flarion does not accelerate run on Spark automatically. The page lists a 'one config change' install and says you can turn it off with one config change to compare.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/faqs",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "tune",
   "fact": "The FAQ says existing Spark tuning carries over and is kept; Flarion changes how the engine executes. The garbage-collection post says native memory is managed off-heap with no GC pauses, but part of a job (driver, planning, unsupported operators, often the final write) still runs on the JVM heap. Telemetry marks each stage native or Spark with runtime and memory.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/faqs",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "stack",
   "fact": "Platforms listed: Databricks (init scripts), Amazon EMR (bootstrap action), Google Cloud Dataproc, Azure HDInsight, Spark on Kubernetes (Helm chart or Spark operator) and on-premises. Frameworks: Scala Spark, PySpark, Trino, Ray. Table formats: Iceberg, Delta Lake, Hudi. File formats: Parquet, Avro, JSON. The benchmark ran Spark 3.5.5 and Databricks 16.4 LTS (Spark 3.5.2). A supported-version list is not published; a blog post mentions staying on Spark 3.4 and gaining newer-Spark benefits.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "where",
   "fact": "No special hardware: Flarion runs CPU-native on the fleet already in use (FAQ contrasts it with GPU accelerators). It is usable on AWS, Azure, GCP, on-premises and air-gapped setups. The company is SOC 2 Type II certified per the home page.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/faqs",
   "read_date": "2026-11-10"
  },
  {
   "option": "Flarion",
   "topic": "profile",
   "fact": "Founders: Ran Reichman (CEO) and Udi Tizan (COO; the bio cites the Granulate $650M exit). Investor logos on the About page: Essence, Hetz Ventures, Sierra Ventures (read from image alt text; no amounts). The product is built on Apache Arrow and DataFusion, and the team says it contributes to those projects, but Flarion itself is proprietary. Footer copyright 2026.",
   "source_type": "vendor",
   "source_url": "https://www.flarion.io/about-us",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "profile",
   "fact": "Lightning Engine is a high-performance execution environment for Apache Spark on Managed Service for Apache Spark that accelerates compute-intensive workloads without requiring changes to Spark code. It targets DataFrame, Dataset and Spark SQL workloads; I/O-bound or RDD-heavy jobs may suit the standard engine.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/docs/guides/lightning-engine",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "profile",
   "fact": "Google announced Lightning Engine in preview on May 30, 2025.",
   "source_type": "vendor",
   "source_url": "https://cloud.google.com/blog/products/data-analytics/introducing-lightning-engine-for-apache-spark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "speed",
   "fact": "Google's launch blog says that at a 10 TB dataset size Lightning Engine accelerates Spark by 3.6x on TPC-H-like workloads versus open source Spark on similar infrastructure. The queries are derived from TPC-H and not comparable to official TPC-H results.",
   "source_type": "vendor",
   "source_url": "https://cloud.google.com/blog/products/data-analytics/introducing-lightning-engine-for-apache-spark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "speed",
   "fact": "The pricing page says Lightning Engine delivers up to 4.9x faster performance than open source Spark and up to 2.5x the price-performance over a high-speed Spark offering Google does not name, with no workload, method or competitor named on the page.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/pricing",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "speed",
   "fact": "The docs claim Native Query Execution on Google Axion ARM (C4A) delivers 2.5x to 4x speedup over open source Spark on analytical workloads. No method is given on the page.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/docs/guides/lightning-engine",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "cost",
   "fact": "Serverless is billed per second in Data Compute Units (DCU, 1-minute minimum). Example us-central1 rates: standard $0.06 per DCU-hour, premium (Lightning Engine) $0.089 per DCU-hour. Clusters pay a management fee plus a Lightning Engine add-on plus Compute Engine VMs and disks.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/pricing",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "rewrite",
   "fact": "Docs say no Spark code changes. Requires image 2.3.3+ or 3.0.2+ (debian13/ubuntu24 for Lightning Engine) and enabling with --engine=lightning at cluster creation. Spark, PySpark, SparkSQL and SparkR jobs are accelerated; other job types run on the standard engine.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/docs/guides/lightning-engine",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "tune",
   "fact": "NQE is not recommended for RDD-heavy jobs, UDFs, most Spark ML libraries or I/O-bound jobs. NQE jobs on GPU accelerators fail. Unsupported inputs include Byte in ORC and Parquet and Struct/Array/Map in Parquet. A qualification tool exists to check jobs.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/docs/guides/lightning-engine",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "stack",
   "fact": "NQE reads Parquet, ORC, Apache Iceberg and Delta Lake. Hudi is covered by general Dataproc docs but not stated for NQE. Runs on x86 Intel and AMD, and ARM Google Axion C4A machines.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/docs/guides/lightning-engine",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "where",
   "fact": "Google Cloud only. Rates on the pricing page are regional (us-central1 example given).",
   "source_type": "vendor-docs",
   "source_url": "https://docs.cloud.google.com/managed-spark/pricing",
   "read_date": "2026-11-10"
  },
  {
   "option": "Google Cloud Lightning Engine (Managed Service for Apache Spark)",
   "topic": "open",
   "fact": "The launch blog footnotes the TPC-H-like derivation but publishes no scripts, cluster spec or raw timings.",
   "source_type": "vendor",
   "source_url": "https://cloud.google.com/blog/products/data-analytics/introducing-lightning-engine-for-apache-spark",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "profile",
   "fact": "The engine is based on two open source components: Velox, a C++ library introduced by Meta, and Apache Gluten (incubating), a middle layer introduced by Intel that offloads JVM SQL engine execution to native engines.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "rewrite",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "tune",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "stack",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "where",
   "fact": "Runs only inside Microsoft Fabric (Azure) on OneLake data. It does not run on AWS EMR or EKS.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "speed",
   "fact": "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.'",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "cost",
   "fact": "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.",
   "source_type": "vendor-docs",
   "source_url": "https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Microsoft Fabric Spark native execution engine",
   "topic": "open",
   "fact": "No benchmark method, data or scripts are published for the engine's speedup on the documentation page.",
   "source_type": "vendor-docs",
   "source_url": "https://learn.microsoft.com/en-us/fabric/data-engineering/native-execution-engine-overview",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "speed",
   "fact": "AWS and NVIDIA report that TPC-DS at 3 TB (103 queries) on 8-node Amazon EMR on EKS clusters ran in 281 seconds on g7.4xlarge GPU instances (NVIDIA RTX PRO 4500 Blackwell) versus 1,010 to 1,043 seconds on comparable CPU instances, which AWS labels a 3.7x speedup. Median of 5 iterations, Spark 3.5.6, cuDF plugin 26.04.2, us-east-1.",
   "source_type": "cloud-provider-docs",
   "source_url": "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_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "speed",
   "fact": "NVIDIA's own FAQ gives a general expectation and says there is no formula for a specific query. This is a vendor claim with no named benchmark behind it.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.nvidia.com/spark-rapids/user-guide/latest/faq.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "speed",
   "fact": "NVIDIA's overview page compares the published AWS GPU result with separate NDS (TPC-DS derived) 3 TB runs of open-source Spark 3.5.6 on EC2. It says the GPU run is 8.4x faster than m7gd.8xlarge and 11.0x faster than m9gd.4xlarge, with 77% and 72% lower reported cost per run. NVIDIA itself notes the runs use different hardware and software stacks.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.nvidia.com/spark-rapids/user-guide/latest/overview.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "cost",
   "fact": "AWS reports cost per benchmark run of $2.06 on the GPU cluster versus $2.93 to $3.18 on the CPU clusters, using On-Demand us-east-1 prices as of May 2026. The g7.4xlarge cluster costs $26.35 per hour (8 x $3.042 EC2 plus $2.01 for EMR on EKS) against $10.43 to $10.99 per hour for the CPU clusters. Cost excludes the EKS control-plane fee, EBS, S3 and the driver pod. The software itself is free; you pay for GPU instances.",
   "source_type": "cloud-provider-docs",
   "source_url": "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_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "rewrite",
   "fact": "NVIDIA says existing Spark applications run with no code change once the plugin is launched and enabled by a configuration setting. Unsupported operators and UDFs fall back to the CPU, so the job completes but those stages are not accelerated.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.nvidia.com/spark-rapids/user-guide/latest/overview.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "rewrite",
   "fact": "Only the DataFrame API (Dataset[Row]) and a limited set of SQL and DataFrame operations are accelerated. Custom classes or types with Dataset, APIs that take Row or Scala/Java functions (flatMap, foreach, foreachPartition), GraphX and RDDs are not accelerated. Structured streaming is not a focus.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.nvidia.com/spark-rapids/user-guide/latest/faq.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "tune",
   "fact": "The user guide has a tuning guide (executors, tasks per executor, pooled and pinned memory, concurrent tasks per GPU, shuffle partitions, input partition size, columnar batch size), an AutoTuner, a Profiling tool and a Qualification tool, plus a recommended-practices section on handling GPU out-of-memory errors. In the AWS test the GPU config set executor memoryOverhead 30G, pinnedPool 8G, concurrentGpuTasks 3 and RapidsShuffleManager, and AWS advises using the Spark History Server to tune concurrentGpuTasks and pinnedPool.size.",
   "source_type": "vendor-docs",
   "source_url": "https://docs.nvidia.com/spark-rapids/user-guide/latest/index.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "tune",
   "fact": "AWS recommends a pre-migration assessment with the NVIDIA qualification tool to estimate GPU acceleration potential, and setting spark.rapids.sql.explain=NOT_ON_GPU to see which operations run on CPU.",
   "source_type": "cloud-provider-docs",
   "source_url": "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_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "stack",
   "fact": "Release v26.10.0 supports Apache Spark 3.3.x, 3.4.x, 3.5.0 to 3.5.9, 4.0.0 to 4.0.4, 4.1.1 to 4.1.3 and 4.2.0 (Scala 2.12 and 2.13 depending on version). Supported Databricks runtimes on AWS and Azure are 14.3 ML LTS (Spark 3.5.0) and 17.3 ML LTS (Spark 4.0.0). Dataproc 2.1 to 2.3 and Dataproc Serverless runtimes 1.2, 2.2 and 3.0 are supported.",
   "source_type": "vendor-docs",
   "source_url": "https://nvidia.github.io/cudf-spark/docs/download.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "stack",
   "fact": "Amazon EMR on EKS natively supports the plugin (release 6.9.0 or later; the '-spark-rapids' release variant ships it pre-installed). The user guide also has a getting-started page for AWS EMR (EC2) and covers Apache Iceberg and Delta Lake support pages, including reading and writing tables.",
   "source_type": "cloud-provider-docs",
   "source_url": "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_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "where",
   "fact": "Needs NVIDIA GPUs: Volta, Turing, Ampere, Ada Lovelace, Hopper and Blackwell generations; tested on V100, T4, A10, A100, L4, H100, B100, RTX PRO 4500 and RTX PRO 6000. Linux with glibc 2.28 or newer; NVIDIA driver R525+ (CUDA 12) or R580+ (CUDA 13). On AWS the benchmark used g7.4xlarge (1 GPU, 16 vCPU, 64 GB RAM); NVIDIA's EMR guide maps m5d.8xlarge to g4dn.8xlarge for T4 GPUs.",
   "source_type": "vendor-docs",
   "source_url": "https://nvidia.github.io/cudf-spark/docs/download.html",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "open",
   "fact": "NVIDIA publishes the NDS benchmark automation (data generation, power and throughput runs) in a public Apache-2.0 repo, with a disclaimer that NDS is derived from TPC-DS and is not comparable to published TPC-DS results. The AWS post publishes the cluster, Spark config, EMR release and pricing method; it does not link scripts.",
   "source_type": "vendor",
   "source_url": "https://raw.githubusercontent.com/NVIDIA/cudf-spark-benchmarks/dev/nds/README.md",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "breadth",
   "fact": "Owner is NVIDIA (copyright 2026 NVIDIA Corporation & Affiliates). The repo LICENSE says source code is Apache-2.0 and documentation is CC-BY-4.0; the GitHub API reports the license as 'other'. Repo created 2020-05-14, about 1,000 stars.",
   "source_type": "vendor",
   "source_url": "https://raw.githubusercontent.com/NVIDIA/cudf-spark/main/LICENSE",
   "read_date": "2026-11-10"
  },
  {
   "option": "NVIDIA RAPIDS Accelerator for Apache Spark (now NVIDIA cuDF plugin for Apache Spark)",
   "topic": "profile",
   "fact": "Recent GitHub releases: v26.10.0 (2026-11-05), v26.08.1 (2026-08-28), v26.08.0 (2026-08-20). Date-based versioning with releases roughly every two months.",
   "source_type": "vendor",
   "source_url": "https://api.github.com/repos/NVIDIA/cudf-spark/releases?per_page=3",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "speed",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "speed",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/post/259-faster-what-microsoft-s-award-winning-sigmod-paper-says-about-the-speedata-apu",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "speed",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "rewrite",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "stack",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/technology",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "where",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "cost",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/product",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "tune",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/workload-analyzer",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "open",
   "fact": "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.",
   "source_type": "vendor",
   "source_url": "https://github.com/Speedata-io",
   "read_date": "2026-11-10"
  },
  {
   "option": "Speedata",
   "topic": "profile",
   "fact": "Company page: founded by semiconductor veterans, including Jonathan Friedmann (Provigent, acquired by Broadcom for over $300M) and Yoav Etsion (Technion professor). CEO Adi Gelvan (co-founder of Speedb, acquired by Redis in 2024) joined in 2025 after a successful chip tape-out. Press list includes a SemiWiki CEO interview (May 17, 2026) and a PR Newswire release on the Nebul partnership (Feb 19, 2026). Partners listed: Dell, HPE, Nebul, Carahsoft, Systemic.fr, Kodata.",
   "source_type": "vendor",
   "source_url": "https://www.speedata.io/company",
   "read_date": "2026-11-10"
  }
 ]
}