<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spark on Home</title><link>https://oedokumaci.com/tags/spark/</link><description>Recent content in Spark on Home</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Oral Ersoy Dokumaci</copyright><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oedokumaci.com/tags/spark/index.xml" rel="self" type="application/rss+xml"/><item><title>Spark vs Hadoop vs DuckDB vs Polars</title><link>https://oedokumaci.com/blog/posts/apache-spark/</link><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><guid>https://oedokumaci.com/blog/posts/apache-spark/</guid><description>One SQL query on 41 million New York taxi trips in an Iceberg table takes 0.29 s with DuckDB, 0.51 s with Polars, and 5.66 s with Spark, all on one laptop. In this chapter, we see how DuckDB and Polars use every core of one machine, how the Google File System, MapReduce, and Hadoop store and process data on many machines, and how Spark works: its cache and lineage, the driver and executors, the query plan, tasks, stages, and shuffles. We also see when one machine is enough and when Spark is worth its costs.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://oedokumaci.com/blog/posts/apache-spark/featured.jpg"/></item></channel></rss>