Maybe it all works, but the paper is not trivial to decipher and the GitHub repository does not seem to exist. It doesn't seem to define what are the inputs to the system (what is a query? UTF-8 text? tokens?) and what are the outputs. It'd really help if the algorithm was written out step by step with all the expected type information included.
At first I thought it was similar to something I've built before as a long-term slowly degrading cache for augmenting an FFN by caching well-learned answers, answering by performing a beam search in the key space resulting in located key accuracy measure (how well it corresponds to the input query) and answer confidence (has it been a long time since verification?), but that's not quite it? It feels similar in some way, but is it?
We handeld llm like a human brain we decopelled knowledge from the memory and build a memory layer that makes redoing things free and fast, so the llm can once it learned something solves it for free the next time
We handeld llm like a human brain we decoupled knowledge from the memory and build a memory layer that makes redoing things free and fast, so the llm can once it learned something solves it for free the next time
"No implementation detail, algorithm, or configuration is contained in this document by design."
+ odd page cuts, it's as-if no human has ever looked at this before uploading it.
These LLMs are absolute poison for some folks.
You couldn't be bothered to write a coherent summary of what this actually is and what it does, you just let the AI write some random noise, eh?
This paper show a new tool called Galahad.Normally, AI has to think and guess the answer every time, which costs time and money.
The knowledge of the model grows next to it not the model itself and no it is not the same as cache
No fine-tuning needed
It gives the exact same right answer every time, costs zero extra tokens, and saves lots of energy
Maybe it all works, but the paper is not trivial to decipher and the GitHub repository does not seem to exist. It doesn't seem to define what are the inputs to the system (what is a query? UTF-8 text? tokens?) and what are the outputs. It'd really help if the algorithm was written out step by step with all the expected type information included.
At first I thought it was similar to something I've built before as a long-term slowly degrading cache for augmenting an FFN by caching well-learned answers, answering by performing a beam search in the key space resulting in located key accuracy measure (how well it corresponds to the input query) and answer confidence (has it been a long time since verification?), but that's not quite it? It feels similar in some way, but is it?
So, you don't know what it is, either.
We handeld llm like a human brain we decopelled knowledge from the memory and build a memory layer that makes redoing things free and fast, so the llm can once it learned something solves it for free the next time
this sounds like ur explaining caching
how is it not the same as a cache it its exact description matches the description of a cache?
100% generated. I skimmed the paper, and came out with a feeling of still not knowing what this is about.
We handeld llm like a human brain we decoupled knowledge from the memory and build a memory layer that makes redoing things free and fast, so the llm can once it learned something solves it for free the next time
Only a single 46Gb GPU? Wow AI sure is amazing tech.
[dead]