Am I able to use graph store for memory storage but not retrieval? #3565
-
|
Since adding memories and retrieving memories are two separate operations, I was wondering if it was possible for me to decouple the configuration used for each. I want to leverage Mem0's ability to populate a graph database with entities and relationships to potentially use in a different context, but then only retrieve from a vector store to optimize for latency (since my use case might not require the temporal benefits that the graph store provides). Is this possible to do? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey @CharlesCreditGenie thank you for reaching out. Yes, that’s possible. You can decouple the configurations by using separate Mem0 client instances — one for adding memories with the graph store enabled, and another for retrieval that only uses the vector store. This way, you can still build your entity graph while keeping retrieval latency low. |
Beta Was this translation helpful? Give feedback.
-
|
Ok great, I will try that, thank you! |
Beta Was this translation helpful? Give feedback.
Hey @CharlesCreditGenie thank you for reaching out. Yes, that’s possible. You can decouple the configurations by using separate Mem0 client instances — one for adding memories with the graph store enabled, and another for retrieval that only uses the vector store. This way, you can still build your entity graph while keeping retrieval latency low.