Re:Using Vectorize to build an unreasonably good search engi...
by leobg on Thursday December 25, 2025 @07:20AM
(#46383977)
Not an apples to apples comparison. Vector search is only fast after you have built an index. The same is true for full text search. That too, will be blazing fast once you have built an index (like Google pre-transformer).
Re:Using Vectorize to build an unreasonably good search engi...
by markerz on Thursday December 25, 2025 @10:05PM
(#46388843)
LLMs will always have the tool call overhead, which I find to be quite expensive (seconds) on most models. Directly using vector databases without the LLM interface gets you a lot of the semantic search ability without the multi-second latency, which is pretty nice for querying documents on a website. E.G. finding relevant pages on a documentation website, showing related pages, etc. Can be applied to GitHub Issues to deduplicate issues, or show existing issues that could match what the user is about to report. There are plenty of places where “cheap and fast” is better and an LLM interface just gets in the way. I think this is a lot of the unsqueezed juice in our industry.
On the other hand, generating and regenerating embeddings for all your documents can be time consuming and costly, depending on how often you need to reindex