Memory retention logic in a memory architecture

Community
1

I would love to get some thoughts/comments from the community on memory retention. I am creating a memory architecture using vector dbs(semantic memory). For example, if a question is asked, i convert to embedding and store in db. Next time do a matching to see if a similar question is asked. I am also implementing memory achival where I calculate a retention value following Ebbinghaus forgetfulness curve R = e(-t/S) . t is the time since the memory object was stored and S is the number of times the memory object is referred. If this score is ~0%, I remove the memory object. Would love to hear any other options

1 Like
2

But do you also store the original question? Otherwise I can’t see why that would be very useful.

3

Yes I store the original question also along with the embedding and a different table to track the number of times referred

1 Like
4

How is this beneficial in your use case?

Database storage is cheap, embedding retrieval is cheap, why delete anything?

5

We see that it will grow a lot as it will be a common store and over a period of time may become the organizational memory. we have the option to turn on/off the retention

2 Likes