๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
280 ํŒ”๋กœ์ž‰ ์ค‘    415 ํŒฌ
๐Ÿ’พ Billion-scale vector search without keeping everything in memory. ๐Ÿ“ฐ Title: HFresh: Memory-Efficient Vector Search ๐Ÿ”— URL: Weaviate introduces HFresh, a new disk-based vector index built to handle billion-vector datasets on constrained memory budgets. Highlights ๐Ÿงฉ Partition-based architecture Instead of connecting every vector in one giant graph like HNSW, HFresh splits vectors into small regions called postings. An in-memory centroid HNSW narrows down the right region, then only the relevant postings are read from disk. ๐Ÿ“ฆ Two-stage quantization Centroids use RQ8, cutting memory about 4x while preserving routing accuracy. Postings use RQ1, compressing up to 32x versus 32-bit floats to minimize disk I/O and storage cost. ๐Ÿ”„ Rebuild-free background maintenance Split, Merge, and Reassign, based on the LIRE protocol, keep the index fresh continuously with no full rebuilds required. On the 1M-vector DBpedia dataset, HFresh used just 239MB of heap versus 6.67GB for uncompressed HNSW, about 28x less. It has also been proven at 1 billion 256-dim vectors, making it a strong fit for memory-constrained, large-scale deployments. #VectorSearch# #Weaviate#
๋” ๋ณด๊ธฐ