<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A performance comparison of Dask and Apache Spark for data-intensive neuroimaging pipelines · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1907.13030/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1907.13030/feed.xml" rel="self" type="application/rss+xml" /><item><title>A performance comparison of Dask and Apache Spark for data-intensive neuroimaging pipelines — mentioned by peterthehacker</title><link>https://news.ycombinator.com/item?id=26136282</link><guid isPermaLink="false">urn:hackerpapers:mention:1907.13030:26136282</guid><pubDate>Sun, 14 Feb 2021 21:09:29 GMT</pubDate><description>&lt;p&gt;I would be interested in seeing some spark v dask benchmarks too. Haven’t seen any yet though. In my experience, Dask really shines when you implement custom numpy computations that could only be done in spark UDFs. We saw a decent performance difference there, but for common built-in computations I’d imagine that spark has better performance. Edit: after some googling I found this paper with benchmarks. https://arxiv.org/pdf/1907.13030.pdf &amp;gt; Results show that despite slight differences between Spark and Dask, both engines perform comparably. However, Dask pipelines risk being limited by…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1907.13030/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
