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
Scanning all collections for deleted files, and removing embeddings and documents where necessary, can be a slow operation. This is done on startup and whenever a folder is updated, and is not interruptible or done in chunks/incrementally. This can mean that requesting an embedding for LocalDocs query lookup in a chat, or even just closing the UI, can take significantly longer than expected. When a chat is waiting on an embedding, this will also block the LLM thread, which can make the UI feel really stuck.
We should find a way to make cleanDB(), which performs this operation, block the database thread for less time, e.g. by making it incremental like scanQueue().
The text was updated successfully, but these errors were encountered:
Scanning all collections for deleted files, and removing embeddings and documents where necessary, can be a slow operation. This is done on startup and whenever a folder is updated, and is not interruptible or done in chunks/incrementally. This can mean that requesting an embedding for LocalDocs query lookup in a chat, or even just closing the UI, can take significantly longer than expected. When a chat is waiting on an embedding, this will also block the LLM thread, which can make the UI feel really stuck.
We should find a way to make cleanDB(), which performs this operation, block the database thread for less time, e.g. by making it incremental like scanQueue().
The text was updated successfully, but these errors were encountered: