pg.ddx.io  pgvector/pgvector GitHub issues and pull requests  
help / color / mirror / Atom feed
From: jkatz (@jkatz) <noreply+jkatz@github.com>
To: pgvector/pgvector <noreply+pgvector-pgvector@github.com>
Subject: Re: [pgvector/pgvector] PR #86: Ivf index prefetch
Date: Wed, 24 May 2023 01:07:55 +0000
Message-ID: <gh-pgvector-pgvector-86-c1560316460@github.com> (raw)
In-Reply-To: <gh-pgvector-pgvector-86@github.com>
References: <gh-pgvector-pgvector-86@github.com>

From my testing, I'm -1 on changing from `BAS_BULKREAD` to `BAS_NORMAL`, though I'd like to test a bit more so I can bring numbers I'm more confident in. For queries under the defaults (i.e. `ivfflat.probes` is `1`), this likely makes little difference. However, increasing the number of probes requires loading more pages into memory, both indexes and heap, and the benefits of `BAS_BULKREAD` becoming noticeable in this case as the vector dimensionality increases.

Assuming that "datasets fit into memory" may work on systems that are exclusively processing vector data, but my current experience from seeing people integrating pgvector is that it exists alongside current workloads.

view thread (11+ messages)  latest in thread

Message-ID: <gh-pgvector-pgvector-86-c1560316460@github.com>
Permalink:  ../gh-pgvector-pgvector-86-c1560316460@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox