Earlier quoted context omitted.
I do about 100 million embeddings using around 50 GPU instances and feed them into Qdrant. Takes about 12 hours. Very happy with the result and performance as long as you have the option to have a very large memory instance running.
Hello from Qdrant. Would like to hear more about your use case. If not yet connected. https://www.linkedin.com/in/zayarni
Why AutoGPT engineers ditched vector databases
51–59 of 59 posts
Re: Why AutoGPT engineers ditched vector databases
#52« AutoGPT engineers » seem to also generate their articles with LLM, making their documentation awful to grok. For instance, after showing 2 commands, we have to suffer this: Forge your future! The forge is your innovation lab. All the boilerplate code is already handled, letting you channel all your creativity into building a revolutionary agent. It's more than a starting point, it's a launchpad for your ideas. In o…
Don't read the intermediate representation. The idea is that you use an LLM to summarize those comments into human readable text.
Re: Why AutoGPT engineers ditched vector databases
#53Has anyone ever managed to generate anything useful with AutoGPT? I had several attempts and apart from wasting some money for GPT-4 API calls, it's never produced anything usable. Whereas if I manually enter prompts in ChatGPT I can often produce simpler project from the beginning till the end, if I partition them into logically independent parts.
Re: Why AutoGPT engineers ditched vector databases
#54Summary: They stopped using vector databases because the performance benefit simply didn't matter compared to how long the LLMs took to respond, and you should focus on using technology to solve problems and not pick the trendy option. But that never got anyone promoted.
So it seems like they still use vectors - they just replaced the search (however that works) with a dot product operation? I mean from a vector point of view that makes total sense
Maybe they found search by plain old dot product faster
Re: Why AutoGPT engineers ditched vector databases
#55Has anyone ever managed to generate anything useful with AutoGPT? I had several attempts and apart from wasting some money for GPT-4 API calls, it's never produced anything usable. Whereas if I manually enter prompts in ChatGPT I can often produce simpler project from the beginning till the end, if I partition them into logically independent parts.
Re: Why AutoGPT engineers ditched vector databases
#56Earlier quoted context omitted.
It can do stuff, sort of, like helping me to create ; https://github.com/tudorw/Ai_MegaList/blob/main/AI_Sector_Br... After a lot of trial and error, I managed to keep it somewhat on track by using a CSV file, something like; "An expert manipulate .csv files, read the first URL from the first line, 2nd column of 'raw.csv', pass the URL to browse_website the questions 'summarize the activities, highlight any investmen…
Are you referring to Waggle Dance or AutoGPT?
Re: Why AutoGPT engineers ditched vector databases
#57Earlier quoted context omitted.
So it seems like they still use vectors - they just replaced the search (however that works) with a dot product operation? I mean from a vector point of view that makes total sense
Searching in LLM land is finding the cosine similarity of two high dimensional vectors. Vector databases try optimizing that operation. Maybe they found search by plain old dot product faster
Re: Why AutoGPT engineers ditched vector databases
#58« AutoGPT engineers » seem to also generate their articles with LLM, making their documentation awful to grok. For instance, after showing 2 commands, we have to suffer this: Forge your future! The forge is your innovation lab. All the boilerplate code is already handled, letting you channel all your creativity into building a revolutionary agent. It's more than a starting point, it's a launchpad for your ideas. In o…
Re: Why AutoGPT engineers ditched vector databases
#59Earlier quoted context omitted.
Searching in LLM land is finding the cosine similarity of two high dimensional vectors. Vector databases try optimizing that operation. Maybe they found search by plain old dot product faster
Cosine what? Isn't it just dot product?
AFAIK cosine similarity or cosine distance is a common one bc it’s faster than a dot product.