<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Understanding Data Storage and Ingestion for Large-Scale Deep Recommendation Model Training · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2108.09373/</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/2108.09373/feed.xml" rel="self" type="application/rss+xml" /><item><title>Understanding Data Storage and Ingestion for Large-Scale Deep Recommendation Model Training — mentioned by benreesman</title><link>https://news.ycombinator.com/item?id=39685337</link><guid isPermaLink="false">urn:hackerpapers:mention:2108.09373:39685337</guid><pubDate>Tue, 12 Mar 2024 21:42:56 GMT</pubDate><description>&lt;p&gt;I think it’s always useful to pay attention to the history on stuff like this and it’s a rare pleasure to be able to give some pointers in the literature along with some color to those interested from first-hand experience. I’d point the interested at the DLRM paper [1]: that was just after I left and I’m sad I missed it. FB got into disagg racks and SDN and stuff fairly early, and we already had half-U dual-socket SKUs with the SSD and (increasingly) even DRAM elsewhere in the rack in 2018, but we were doing huge NNs for recommenders and rankers even for then. I don’t know if this is…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2108.09373/"&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>
