biggraph-wikidata-search-with-weaviate VS qdrant

* Wikidata dataset: https://github.com/semi-technologies/biggraph-wikidata-searc...

Last week there was also a feature on Techcrunch about vector search and Weaviate:

I took Qdrant for this project. The reason was that Qdrant stands for high-performance vector search, the best choice against use cases like finding similar function calls based on semantic similarity. Qdrant is not only powerful but also scalable to support a variety of advanced search features that are greatly useful to nuanced caching mechanisms like ours.

I'm currently looking to implement locally, using QDrant [1] for instance.

I'm just playing around, but it makes sense to have a runnable example for our users at work too :) [2].

[1]. https://qdrant.tech/

Also compare with qdrant's Rust implementation; they tout their performance. https://github.com/qdrant/qdrant/tree/master/lib/segment/src...

There are much better known examples, such as https://qdrant.tech/ and https://github.com/lancedb/lancedb

For more information, see our release notes. Qdrant is an open source project. We welcome your contributions; raise issues, or contribute via pull requests!

Initialize the Qdrant Client with in-memory storage. The collection name will be “imagebind_data” and we will be using cosine distance.

Qdrant is an open-source vector search engine optimized for performance and flexibility. It supports both exact and approximate nearest neighbor search, providing a balance between accuracy and speed for various AI and ML applications.

Qdrant serves as a vector database, optimized for handling high-dimensional data typically found in AI and ML applications. It's designed for efficient storage and retrieval of vectors, making it an ideal solution for managing the data produced and consumed by AI models like Mistral 7B. In our setup, Qdrant handles the storage of vectors generated by the language model, facilitating quick and accurate retrievals.