3 ms·
Redis uses too much memory and supports only two NN algorithms FLAT (very slow) and HNSW if you start indexing millions of large vectors you will quickly unders
by ttt3ts 4y ago
Redis uses too much memory and supports only two NN algorithms FLAT (very slow) and HNSW if you start indexing millions of large vectors you will quickly understand the problem.
That being said, many of these DBs are overcomplicated for most use cases. Redis HNSW will work for many use cases.
- winddude 4y agoit uses a lot of memory because it's an in memory db, that's by design.
- spartee 4y agoEnterprise has tiered memory. We have customers in the 50-100m range. benchmarked more than that as well. Single query latency will usually be better than most of the field. Also, were working on other variants of our index that will scale to 500m + More to come. https://github.com/redisventures https://github.com/redisventures to keep up with our team
- fzliu 4y agoRedis does fairly well single-threaded - iirc it does better than Milvus. The problem is, once you move to larger applications and want higher performance, its architectural limitations make it impossible to scale.