Загрузка видео...

Не удалось загрузить видео

На главную

This is cool. I used Jev to improve my custom memory system. Results: → 94% fewer tokens used → 2–3× faster memory retrieval This was just a quick test, but I believe it opens up so many new opportunities.

28,771 просмотров • 1 день назад •via X (Twitter)

Комментарии: 10

Фото профиля Jose Rosado @ WebScale
Jose Rosado @ WebScale1 день назад

very cool

Фото профиля Daniel Priscu
Daniel Priscu1 день назад

Another great idea for Jev utilization. well done.

Фото профиля WhiteMale
WhiteMale1 день назад

How much more efficient is this than RAG + vector database?

Фото профиля Mirza
Mirza1 день назад

Interesting idea, what is special about your "custom memory system"? Why not use Mem0 or Honcho?

Фото профиля Moritz Kremb
Moritz Kremb1 день назад

i’ve tried mem0 and fabric but it’s kind of overkill for my use case sth like QMD might actually be useful, not sure if that would be better than this Jev system, i’d have to test it

Фото профиля lilyyy🦢🛍️
lilyyy🦢🛍️1 день назад

How I use it ?

Фото профиля Alek
Alek1 день назад

does retrieval stay stable as memory grows?

Фото профиля Ishwar | Infrastructure Systems
Ishwar | Infrastructure Systems1 день назад

this is the part I’d want to measure next: does the 94% token reduction in memory retrieval actually translate into less repeated context in the LLM loop? I’ve seen a coding-agent session hit 99% repeated context, so I’m curious how much of that can actually be eliminated by a better memory layer.

Фото профиля George Hanu | Coding with AI
George Hanu | Coding with AI1 день назад

This might be one of the best Jev use cases I’ve seen. Don’t make the big model read the whole memory. Let Jev decide what’s relevant first, then spend tokens only on the small slice that matters. 👀

Фото профиля Manoj Kumar Nayak 🇮🇳
Manoj Kumar Nayak 🇮🇳1 день назад

Today I also did same. It is really fast and efficient.

Похожие видео