Find answers from the community

Updated 3 months ago

I have a question regarding the use of a

I have a question regarding the use of a global lock in this llama-index guide to support concurrent reads/writes. Does using llama-index's wrappers for remote vector DBs actually require locking? or is this used in the example only because of the use of SimpleDirectoryReader as the vector store?

3 comments

LLogan M

oh my, havent seen that guide in a while haha

It might be overkill in this example, but was just trying to play it safe. 3rd party vector dbs hopefully handle concurrent reads and writes nicely 🙂

ttenz

thanks for the response Logan, if the 3rd party vector dbs do (we're using opensearch and have seen no reason to believe it doesnt), can we forego locking? I was worried that llama-index internally is caching data returned from calls to VectorStoreIndex and that is why locking is necessary

LLogan M

ya you should be fine to forgo locking in that case

Add a reply