Earlier quoted context omitted.
Embeddings are vectors of chunks of documents, lists of 1024 (depending on a model) float numbers that represent that short snippet of text. This kind of search works by finding the most similar vectors, calculating them cost fractions of the cent, but when you need to do it billions to trillions of times, it adds up.
You could likely calculate them all on a modern MacBook easily enough. Searching the embeddings is a different problem, but there are lots of specialised databases that can make it efficient.
Search ArXiv Fluidly
11–16 of 16 posts
Re: Search ArXiv Fluidly
#12Did they calculate embeddings for the entire archive? That must have cost a fortune.
Re: Search ArXiv Fluidly
#13Did they calculate embeddings for the entire archive? That must have cost a fortune.
I think doing it locally with an open source model would be a lot cheaper as well. Especially because they wouldn't have to keep using OpenAI's API for each new query.
Edit: I overlooked the about page (https://searchthearxiv.com/about), seems like they *are* using OpenAI's API, but they only have 300K papers indexed, use an older embedding model, and only calculate embeddings on the abstract. So this should be pretty cheap.
Re: Search ArXiv Fluidly
#14Re: Search ArXiv Fluidly
#15Re: Search ArXiv Fluidly
#16It is pretty good, https://searchthearxiv.com/?q=https%3A%2F%2Farxiv.org%2Fabs%... If this is your project, please talk about how you made it.
Code is on github https://github.com/augustwester/searchthearxiv