<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Billion-scale similarity search with GPUs · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1702.08734/</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/1702.08734/feed.xml" rel="self" type="application/rss+xml" /><item><title>Billion-scale similarity search with GPUs — HN submission</title><link>https://news.ycombinator.com/item?id=48398689</link><guid isPermaLink="false">urn:hackerpapers:submission:1702.08734:48398689</guid><pubDate>Thu, 04 Jun 2026 13:54:28 GMT</pubDate><description>&lt;p&gt;Inside FAISS: Billion-Scale Similarity Search&lt;/p&gt;&lt;p&gt;Author here. I wrote this as a visual companion to the 2017 FAISS paper (https://arxiv.org/abs/1702.08734), focused on the parts I found hardest to grok from text alone. The article covers a subset of what FAISS does, with the paper as the source of truth. NSG, FastScan, IMI are not covered here, they&amp;#x27;ll get their own articles. I&amp;#x27;d be especially interested in feedback on: - the IVFPQ / IVFADC explanation, particularly the LUT reuse argument - whether the GPU part captures enough of the actual complexity Happy to answer questions.&lt;/p&gt;&lt;p&gt;74 points; 6 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — mentioned by jhj</title><link>https://news.ycombinator.com/item?id=38975511</link><guid isPermaLink="false">urn:hackerpapers:mention:1702.08734:38975511</guid><pubDate>Fri, 12 Jan 2024 23:19:49 GMT</pubDate><description>&lt;p&gt;The implementations that I am aware of, including the one in Faiss which I wrote (described in detail in https://arxiv.org/abs/1702.08734), do not index the vector based on its PQ encoding (e.g., in IVFPQ). The IVF cell chosen in which to put the vector is based on its pre-quantized (full precision floating point) representation. It would lose too much precision to perform all comparisons in the compressed space. Also, distance comparisons are usually of the &amp;quot;ADC&amp;quot; (asymmetric distance comparison) form: the query vector is in full floating point format, and vectors, if quantized/compressed in…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — HN submission</title><link>https://news.ycombinator.com/item?id=36053750</link><guid isPermaLink="false">urn:hackerpapers:submission:1702.08734:36053750</guid><pubDate>Wed, 24 May 2023 03:33:10 GMT</pubDate><description>&lt;p&gt;Billion-scale similarity search with GPUs (2017)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — mentioned by PaulHoule</title><link>https://news.ycombinator.com/item?id=35107858</link><guid isPermaLink="false">urn:hackerpapers:mention:1702.08734:35107858</guid><pubDate>Sat, 11 Mar 2023 12:44:51 GMT</pubDate><description>&lt;p&gt;Depends on what you want to optimize for. See this paper https://arxiv.org/abs/1702.08734 And this library that it describes https://github.com/facebookresearch/faiss Which is an optimal use of your time as you can install it in a minute with anaconda if you use Python.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — HN submission</title><link>https://news.ycombinator.com/item?id=26239780</link><guid isPermaLink="false">urn:hackerpapers:submission:1702.08734:26239780</guid><pubDate>Tue, 23 Feb 2021 17:09:49 GMT</pubDate><description>&lt;p&gt;Billion-scale similarity search with GPUs (FB AI research, 2017)&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — HN submission</title><link>https://news.ycombinator.com/item?id=13800235</link><guid isPermaLink="false">urn:hackerpapers:submission:1702.08734:13800235</guid><pubDate>Mon, 06 Mar 2017 02:07:52 GMT</pubDate><description>&lt;p&gt;Billion-scale similarity search with GPUs&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Billion-scale similarity search with GPUs — HN submission</title><link>https://news.ycombinator.com/item?id=13790720</link><guid isPermaLink="false">urn:hackerpapers:submission:1702.08734:13790720</guid><pubDate>Sat, 04 Mar 2017 13:02:06 GMT</pubDate><description>&lt;p&gt;Billion-scale Similarity Search with GPUs&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1702.08734/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item></channel></rss>
