<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MemoRAG: Boosting Long Context Processing with Global Memory-Enhanced Retrieval Augmentation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2409.05591/</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/2409.05591/feed.xml" rel="self" type="application/rss+xml" /><item><title>MemoRAG: Boosting Long Context Processing with Global Memory-Enhanced Retrieval Augmentation — mentioned by spmurrayzzz</title><link>https://news.ycombinator.com/item?id=41604558</link><guid isPermaLink="false">urn:hackerpapers:mention:2409.05591:41604558</guid><pubDate>Fri, 20 Sep 2024 18:48:19 GMT</pubDate><description>&lt;p&gt;&amp;gt; they have some long-context &amp;quot;Memory Model&amp;quot; (whose details I&amp;#x27;ve yet to fully understand) Section 2.2 of the paper[1] goes into this in more detail. They pretrain the draft model using the redpajama dataset, followed by a supervised fine-tuning step. The training objective &amp;quot;aims to maximize the generation probability of the next token given the KV cache of the previous memory tokens&amp;quot;. This suggests that any model with long context and good retrieval performance could do the same job (and maybe better in the case of the SOTA frontier models). [1] https://arxiv.org/pdf/2409.05591&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2409.05591/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>MemoRAG: Boosting Long Context Processing with Global Memory-Enhanced Retrieval Augmentation — mentioned by diggan</title><link>https://news.ycombinator.com/item?id=41604380</link><guid isPermaLink="false">urn:hackerpapers:mention:2409.05591:41604380</guid><pubDate>Fri, 20 Sep 2024 18:27:34 GMT</pubDate><description>&lt;p&gt;I think leaving just an overview in the repository is fine considering they&amp;#x27;ve released a paper describing it in detail (https://arxiv.org/pdf/2409.05591, linked in the README).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2409.05591/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>MemoRAG: Boosting Long Context Processing with Global Memory-Enhanced Retrieval Augmentation — mentioned by jszymborski</title><link>https://news.ycombinator.com/item?id=41603525</link><guid isPermaLink="false">urn:hackerpapers:mention:2409.05591:41603525</guid><pubDate>Fri, 20 Sep 2024 16:28:40 GMT</pubDate><description>&lt;p&gt;Ok, I think I get it now from scanning the paper and reading Eq. 1 and 2. Normally RAG just sends your query `q` to a information retrieval function which searches a database of documents using full-text search or vector search. Those documents are then passed to a generative model along with your query to give you your final answer. MemoRAG instead immediately passes `q` to a generative model to generate some uninformed response `y`. `y` is then passed to the information retrieval function. Then, just like vanilla RAG, `q` and the retrieved documents are sent to a generative model to give…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2409.05591/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
