|
|
|
|
|
|
by nostrebored
881 days ago
|
|
|
For a comparison of existing assistants API vs. vector search, you can check out my blog at https://nostrebored.com At a high level there are a few differences - Control over embeddings. What gets embedded? What are the output vectors? What models do you use? How do you handle multimodal input? - Performance. When you make a call to Assistants, you have to wait for the Assistant to understand that it needs to do RAG. This performance hit is actually quite large (look at the two videos on the blog for reference) - Cost. OpenAI has an incentive to load the context window to consume more tokens. A few dozen calls to Assistants was costing me around $10. |
|
|
Sorry, but I am not going to read it as it is not an apple to apple comparison atm. OpenAI just released its assistants APIs literally just weeks ago, when so called vector databases have been burning money for ages. You can write a thesis on how those vendors are doing slightly better for now, that won't be the big picture showing the reality on the ground. All those minor issues & unreasonable restrictions can be solved & removed, I don't see any real challenge for openai to implement them. Give openai a few months, they will convince most vector database vendors & gamblers to pack up and leave the field.