3 ms·
Why are they a pain in the...?
by gk1 6y ago
Why are they a pain in the...?
- phenkdo 6y agothe usual yet-another-moving-part (YAMP) complexity.
- EmilStenstrom 6y agoThey typically load all data in memory, so you still need persistence to handle crashes (two setups). And since data is typically huge you need servers with lots of expensive RAM.
- patelajay285 6y agoCheck out Magnitude, we built it to solve that problem: https://github.com/plasticityai/magnitude https://github.com/plasticityai/magnitude It's still loaded from a file, but heavily uses memory-mapping and caching to be speedy and not overload your RAM immediately. And in production scenarios, multiple worker processes can share that memory due to the memory mapping. Granted it's read-only, so might not be exactly what you are looking for. Disclaimer: I'm the author.
- rkt08 6y agoHow about a vector oriented 'database' instead? Pinecone(https://www.pinecone.io/ https://www.pinecone.io/) does both exact and approx search and it's fully managed so you don't have to worry about reliability,availability etc. PS: I work there