<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Faster Matrix Multiplication via Asymmetric Hashing · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2210.10173/</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/2210.10173/feed.xml" rel="self" type="application/rss+xml" /><item><title>Faster Matrix Multiplication via Asymmetric Hashing — mentioned by barfbagginus</title><link>https://news.ycombinator.com/item?id=39722924</link><guid isPermaLink="false">urn:hackerpapers:mention:2210.10173:39722924</guid><pubDate>Sat, 16 Mar 2024 02:51:20 GMT</pubDate><description>&lt;p&gt;I made two really bad misunderstandings which I completely own. I can&amp;#x27;t seem to edit it, so please let this be my refutation and explanation of my own mistake. First misunderstanding: I assumed this was a new large matrix multiplication algorithm building on the hype from last week or so where we saw this paper: https://arxiv.org/abs/2210.10173 It is not an algorithm, but a hardware design - a systolic array using roughly half of the silicon area of a baseline design. 2. Assuming that we were talking about an algorithm, I then further assumed that it reduce an algorithm&amp;#x27;s multiplications by…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2210.10173/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item><item><title>Faster Matrix Multiplication via Asymmetric Hashing — mentioned by anchovy_</title><link>https://news.ycombinator.com/item?id=36327565</link><guid isPermaLink="false">urn:hackerpapers:mention:2210.10173:36327565</guid><pubDate>Wed, 14 Jun 2023 15:37:28 GMT</pubDate><description>&lt;p&gt;&amp;gt;However, an O(n^3) algorithm will always loose out to an O(n^2*log(n)) algorithm, when the input gets big enough. Sure, this might be the case from a theoretical point of view (as per definition) but this completely disregards the hidden constants that come to light when actually implementing an algorithm. There&amp;#x27;s a reason why for instance a state-of-the-art matrix multiplication algorithm [0] can be completely useless in practice: The input data will never become large enough in order to amortize the introduced overhead. [0] https://arxiv.org/abs/2210.10173&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2210.10173/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item></channel></rss>
