<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accelerating Large-Scale Inference with Anisotropic Vector Quantization · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1908.10396/</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/1908.10396/feed.xml" rel="self" type="application/rss+xml" /><item><title>Accelerating Large-Scale Inference with Anisotropic Vector Quantization — mentioned by peter_l_downs</title><link>https://news.ycombinator.com/item?id=40516237</link><guid isPermaLink="false">urn:hackerpapers:mention:1908.10396:40516237</guid><pubDate>Wed, 29 May 2024 19:55:20 GMT</pubDate><description>&lt;p&gt;&amp;gt; JVector, the library that powers DataStax Astra vector search, now supports indexing larger-than-memory datasets by performing construction-related searches with compressed vectors. This means that the edge lists need to fit in memory, but the uncompressed vectors do not, which gives us enough headroom to index Wikipedia-en on a laptop. It&amp;#x27;s interesting to note that JVector accomplishes this differently than how DiskANN described doing it. My understanding (based on the links below, but I didn&amp;#x27;t read the full diff in #244) is that JVector will incrementally compress the vectors it is using…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1908.10396/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Accelerating Large-Scale Inference with Anisotropic Vector Quantization — mentioned by contravariant</title><link>https://news.ycombinator.com/item?id=23996625</link><guid isPermaLink="false">urn:hackerpapers:mention:1908.10396:23996625</guid><pubDate>Thu, 30 Jul 2020 10:44:46 GMT</pubDate><description>&lt;p&gt;In case anyone else was confused why they didn&amp;#x27;t just project onto q first if they want to have &amp;lt;q,x&amp;#x27;&amp;gt; as close as possible to the original &amp;lt;q,x&amp;gt;. Apparently q is a random query vector and their research shows how to define an alternative quantization loss where you weigh quantization loss more heavily when |&amp;lt;q,x&amp;gt;| is high [1]. It&amp;#x27;s worth noting that without this additional weighting you end up with the euclidean distance under the assumption that q is distributed symmetrically. [1]: https://arxiv.org/abs/1908.10396&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1908.10396/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Accelerating Large-Scale Inference with Anisotropic Vector Quantization — mentioned by greenyoda</title><link>https://news.ycombinator.com/item?id=23754380</link><guid isPermaLink="false">urn:hackerpapers:mention:1908.10396:23754380</guid><pubDate>Tue, 07 Jul 2020 00:34:51 GMT</pubDate><description>&lt;p&gt;If someone is looking for the referenced paper (Accelerating Large-Scale Inference with Anisotropic Vector Quantization), it can be found here: https://arxiv.org/abs/1908.10396 (It&amp;#x27;s also linked in the repository&amp;#x27;s docs/algorithms.md, to which there&amp;#x27;s a link at the bottom of the main page.)&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1908.10396/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
