<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI and Memory Wall · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2403.14123/</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/2403.14123/feed.xml" rel="self" type="application/rss+xml" /><item><title>AI and Memory Wall — mentioned by refibrillator</title><link>https://news.ycombinator.com/item?id=41470771</link><guid isPermaLink="false">urn:hackerpapers:mention:2403.14123:41470771</guid><pubDate>Sat, 07 Sep 2024 00:46:29 GMT</pubDate><description>&lt;p&gt;This paper is light on background so I’ll offer some additional context: As early as the 90s it was observed that CPU speed (FLOPs) was improving faster than memory bandwidth. In 1995 William Wulf and Sally Mckee predicted this divergence would lead to a “memory wall”, where most computations would be bottlenecked by data access rather than arithmetic operations. Over the past 20 years peak server hardware FLOPS has been scaling at 3x every 2 years, outpacing the growth of DRAM and interconnect bandwidth, which have only scaled at 1.6 and 1.4 times every 2 years, respectively. Thus for…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2403.14123/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
