<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>In-place Parallel Super Scalar Samplesort (IPS$^4$o) · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1705.02257/</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/1705.02257/feed.xml" rel="self" type="application/rss+xml" /><item><title>In-place Parallel Super Scalar Samplesort (IPS$^4$o) — mentioned by ipsofacto</title><link>https://news.ycombinator.com/item?id=23213874</link><guid isPermaLink="false">urn:hackerpapers:mention:1705.02257:23213874</guid><pubDate>Sun, 17 May 2020 18:09:58 GMT</pubDate><description>&lt;p&gt;There&amp;#x27;s an even better branch-free (super scalar) sorting algorithm: &amp;quot;In-place Parallel Super Scalar Samplesort (IPS4o)&amp;quot; which we started using: https://github.com/SaschaWitt/ips4o https://arxiv.org/abs/1705.02257 As an example, to sort 10 million random longs on my computer it takes std::sort 766 ms (roughly in line with Andrei&amp;#x27;s numbers) and ips4o::sort takes 274 ms. [edit:formatting]&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1705.02257/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item><item><title>In-place Parallel Super Scalar Samplesort (IPS$^4$o) — mentioned by lorenzhs</title><link>https://news.ycombinator.com/item?id=17884612</link><guid isPermaLink="false">urn:hackerpapers:mention:1705.02257:17884612</guid><pubDate>Fri, 31 Aug 2018 11:28:11 GMT</pubDate><description>&lt;p&gt;Especially when targeting realistic machine models, there are a lot of things that are suboptimal about the classical sorting algorithms like quicksort or mergesort. For example, a quicksort with perfect choice of pivot will incur a branch miss with probability 50% for every element. That&amp;#x27;s not something classical complexity analysis measures, but on actual CPUs, branch misses have quite an impact (something like 10–15 cycles). Shameless plug for something I once built for a lecture to demonstrate this: https://github.com/lorenzhs/quicksort-pivot-imbalance For sorting algorithms that take the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1705.02257/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item><item><title>In-place Parallel Super Scalar Samplesort (IPS$^4$o) — mentioned by lorenzhs</title><link>https://news.ycombinator.com/item?id=14669267</link><guid isPermaLink="false">urn:hackerpapers:mention:1705.02257:14669267</guid><pubDate>Fri, 30 Jun 2017 08:08:06 GMT</pubDate><description>&lt;p&gt;Don&amp;#x27;t count out sample-sort just yet, it lends itself to parallelisation very well and is blazingly fast. See https://arxiv.org/abs/1705.02257 (to be presented at ESA in September) for an in-place parallel implementation that overcomes the most important downsides of previous sample-sort implementations (linear additional space).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1705.02257/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item><item><title>In-place Parallel Super Scalar Samplesort (IPS$^4$o) — mentioned by lorenzhs</title><link>https://news.ycombinator.com/item?id=14669239</link><guid isPermaLink="false">urn:hackerpapers:mention:1705.02257:14669239</guid><pubDate>Fri, 30 Jun 2017 07:59:15 GMT</pubDate><description>&lt;p&gt;To illustrate the point about branch misprediction, I implemented quicksort with intentionally skewed pivot selection. You can see the results here: https://github.com/lorenzhs/quicksort-pivot-imbalance For this demo I&amp;#x27;m sorting a permutation of the range 1 to n, so obtaining perfect or arbitrarily skewed pivots is free, which isn&amp;#x27;t realistic, but that&amp;#x27;s not the point. My experiments show that quicksort is fastest on my machine when 15% of the elements are on one side and 85% on the other. This is a tradeoff between branch prediction (if it always guesses &amp;quot;right side&amp;quot;, it&amp;#x27;s right 85% of the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1705.02257/"&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>
