You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
long-running server executing search requests against qdrant database: should it keep the client connection open, or create a new client and then close it after serving each request?
#768
I've created a chatbot server, which uses a QdrantClient instance to execute searches against the database (via a langchain QdrantVectorStore instance): should I keep the client instance connection open as long as my server is running? Or should I create a new client instance each time I receive an HTTP request and then close it again after it's served the request? (And if the latter, it would be great if there was a QdrantClient.reopen() method, because the QdrantVectorStore class doesn't provide a way to update the client if the old client instance is closed and a new client instance is created!).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've created a chatbot server, which uses a
QdrantClientinstance to execute searches against the database (via a langchainQdrantVectorStoreinstance): should I keep the client instance connection open as long as my server is running? Or should I create a new client instance each time I receive an HTTP request and then close it again after it's served the request? (And if the latter, it would be great if there was aQdrantClient.reopen()method, because theQdrantVectorStoreclass doesn't provide a way to update the client if the old client instance is closed and a new client instance is created!).Beta Was this translation helpful? Give feedback.
All reactions