# DualBird blog Part 2: why data skew costs less on its FPGA architecture

News, 1 Sep 2026

**The short answer.** DualBird published Part 2 of its Faster Spark series on September 1, 2026, written by its chief architect and co-founder. The post says Spark gives each running task about 1/N of the shared execution memory, and argues its FPGA architecture reduces the impact of hot-key skew without repartitioning or salting.

DualBird published Faster Spark Was the Goal. A Simpler Spark Came with It: Part 2 on September 1, 2026. The author is listed as Ehud Eliaz, Chief Architect and Co-Founder. The post is about hot-key skew, not high cardinality.

It states that in standard Spark each running task gets roughly 1/N of the executor's shared execution memory regardless of its data, and that a hot key concentrates in one shuffle-read task, so a stage waits for its slowest task. DualBird says its dedicated hardware (FPGA) architecture makes the same skewed data much less of a problem.

This is DualBird's own argument. The post as read on 2026-11-10 gives no benchmark figure in the portion read. A team with skewed joins can compare it with Spark's adaptive query execution skew join handling, which the post says covers joins only.

## Sources

- DualBird blog: Faster Spark Was the Goal, Part 2: https://dualbird.io/resources/blog/faster-spark-part2 (read 10 Nov 2026)
- DualBird resources: https://dualbird.io/resources (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://sparkaccelerationcompare.com/news/dualbird-skew-part-2/
