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
Since the implementation of #99 in Aug 2023, the server has been chugging away producing vector embeddings for all indexed content. However, as per https://blog.searchmysite.net/posts/four-year-retrospective/ , the results of the vector search (used by the Retrieval Augmented Generation) haven't been good enough to make the links to the new search visible on the main site. So basically it has been burning a lot of CPU power for well over a year for no good reason.
This change is to disable the embedding creation, so that indexing can complete more quickly. It would be sensible to delete all existing embeddings, so that they don't become stale.
All the vector search code should be left in so that it can easily be re-enabled at a later date if required.
The text was updated successfully, but these errors were encountered:
I've removed the models container, and stopped the content_chunks creation, so that should save a little on space and a lot on indexing time. I haven't deleted existing embeddings just yet, and there is still a lot of the vector search code and config around, so leaving this open for now.
Since the implementation of #99 in Aug 2023, the server has been chugging away producing vector embeddings for all indexed content. However, as per https://blog.searchmysite.net/posts/four-year-retrospective/ , the results of the vector search (used by the Retrieval Augmented Generation) haven't been good enough to make the links to the new search visible on the main site. So basically it has been burning a lot of CPU power for well over a year for no good reason.
This change is to disable the embedding creation, so that indexing can complete more quickly. It would be sensible to delete all existing embeddings, so that they don't become stale.
All the vector search code should be left in so that it can easily be re-enabled at a later date if required.
The text was updated successfully, but these errors were encountered: