HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
qhjqhj00
MemoRAG
Python2024–2024
qhjqhj00 / MemoRAG

MemoRAG

Empowering RAG with a memory-based data interface for all-purpose applications!

3Distinct people
3Mentions
0Explicit recommenders
2.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Empowering RAG with a memory-based data interface for all-purpose applications!

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2024-09-20 14:41:16 UTC to 2024-09-20 18:14:02 UTC.

012024-09-20 14:00:00 UTC to 2024-09-20 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 20, 14:002024-09-20 15:00:00 UTC to 2024-09-20 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-20 16:00:00 UTC to 2024-09-20 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20, 16:002024-09-20 17:00:00 UTC to 2024-09-20 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-09-20 18:00:00 UTC to 2024-09-20 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 20, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20, 14:002024-09-20 14:00:00 UTC2024-09-20 15:00:00 UTC110
Sep 20, 15:002024-09-20 15:00:00 UTC2024-09-20 16:00:00 UTC000
Sep 20, 16:002024-09-20 16:00:00 UTC2024-09-20 17:00:00 UTC000
Sep 20, 17:002024-09-20 17:00:00 UTC2024-09-20 18:00:00 UTC101
Sep 20, 18:002024-09-20 18:00:00 UTC2024-09-20 19:00:00 UTC101

What Hacker News says

1 sources
In the past, this might have been called an "expert system". Heh, it comes full circle... After ~50 years of Expert Systems winter, we're training our new AGIs to become more specialized! This is a memorable lesson that binaries must always be deconstructed, at least to some extent -- kinda like the endless dance we're doing between monoliths and microservices as each new generation of tools runs into the problems inherent in each. I am naive about LLM technology so I'm not sure about the details or the nomenclature You've got all the details right though, so that's pretty impressive :). AFAICT from a quick glance at the code (https://github.com/qhjqhj00/MemoRAG/blob/main/memorag/memora...), it is indeed "fine tuning" (jargon!) a model on your chosen book, presumably in the most basic/direct sense: asking it reproduce sections of tex
Read the rest
t at random from the book given their surrounding context, and rewarding/penalizing the neural network based on how well it did. The comment mentions GPU memory in the Colab Notebook merely because this process is expensive -- "fine tuning" is the same thing as "training", just with a nearly-complete starting point. Thus the call to `AutoModelForCausalLM.from_pretrained()`. To answer your question explicitly: the fine-tuning step creates a modified version of the base model as an "offline" step, so the memory requirements during inference (aka "online" operation) are unaffected. Both in terms of storage and in terms of GPU VRAM. I'm not the dev tho so obv apologies if I'm off base! I would passionately argue that that step is more of a small addition to the overall pipeline than a core necessity, though. Fine-tuning is really good for teaching a model to recreate style, tone, structure, and other linguistic details, but it's not a very feasible way to teach it facts. That's what "RAG" is for: making up for this deficiency in fine-tuning. In other words, this repo is basically like that post from a few weeks back that was advocating for "modular monoliths" that employ both strategies (monolith vs. microservices) in a deeply collaborative way. And my reaction is the same: I'm not convinced the details of this meshing will be very revolutionary, but the idea itself is deceptively clever!
In MemoRAG – Enhance RAG with memory-based knowledge discovery for long contexts

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.