<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CAGRA: Highly Parallel Graph Construction and Approximate Nearest Neighbor Search for GPUs · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2308.15136/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2308.15136/feed.xml" rel="self" type="application/rss+xml" /><item><title>CAGRA: Highly Parallel Graph Construction and Approximate Nearest Neighbor Search for GPUs — mentioned by fzliu</title><link>https://news.ycombinator.com/item?id=39030837</link><guid isPermaLink="false">urn:hackerpapers:mention:2308.15136:39030837</guid><pubDate>Wed, 17 Jan 2024 17:37:28 GMT</pubDate><description>&lt;p&gt;You need different indexing algorithms for different use cases - brute-force indexing, for example, is &amp;quot;SOTA&amp;quot; when it comes to recall (100%). If you have multiple use cases or if you might have domain shift, you&amp;#x27;ll want a vector database that supports multiple indexes. Here&amp;#x27;s my 2¢: - If you&amp;#x27;re just playing around with vector search locally and have a very small dataset, use brute-force search. Don&amp;#x27;t worry about indexes until later. - If you have plenty of RAM and CPU cores and would like to squeeze out the most performance, use ScaNN or HNSW plus some form of quantization (product…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2308.15136/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item></channel></rss>
