Spot the error in this candidate's description of IVF's two main parameters.

Attempt it

Click any words you think contain an error. Click again to unmark.

Mark at least one word to submit.

Quick reference

TL;DR

The candidate swapped the roles. nlist is BUILD-TIME (number of k-means clusters); nprobe is QUERY-TIME (how many clusters each query scans, the recall knob).

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

IVF splits all your vectors into buckets. nlist is how many buckets you make (decided once when you build the index, like deciding how many filing cabinets to buy). nprobe is how many buckets each query looks inside (decided per query, like deciding whether to check 1 cabinet or 10 when you are looking for something). The candidate mixed them up.

Key concepts

IVF index K-means clustering

Quick scan · 2–4 min

Everything important, quickly.

Walk the IVF lifecycle: nlist drives k-means at build, fixes the partition structure; nprobe is the runtime knob that picks how many partitions to scan, trading recall for latency. Discuss why the confusion is so common and what tuning workflow uses each correctly.

Code example

python

import faiss
import numpy as np

d = 768
n_vectors = 1_000_000
nlist = int(n_vectors ** 0.5)            # ~1000 clusters, BUILD-TIME
quantizer = faiss.IndexFlatL2(d)
index = faiss.IndexIVFFlat(quantizer, d, nlist)

data = np.random.randn(n_vectors, d).astype('float32')
index.train(data)                         # k-means: this is what nlist controls
index.add(data)

query = np.random.randn(1, d).astype('float32')

# QUERY-TIME knob - changeable per request, no rebuild needed
index.nprobe = 1
D, I = index.search(query, k=10)          # fast, lower recall

index.nprobe = 32
D, I = index.search(query, k=10)          # slower, higher recall

Real-world examples

Real products, models, and research that use this idea.

FAISS IndexIVFFlat exposes nlist as a constructor argument (build-time) and index.nprobe as a runtime attribute (query-time); the API split mirrors the lifecycle split.
Milvus IVF index documentation explicitly warns against confusing nlist (set at index creation) with nprobe (set in search request).
Pinecone's p2 pods use IVF-PQ internally with nlist fixed per pod and nprobe exposed via the top_k and search-quality knobs.
OpenSearch's IVF implementation requires nlist at index time and exposes nprobe via the search query body.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWhat rule of thumb sets nlist?

Sign in or go Pro to see the approach for this follow-up.

QHow does raising nprobe affect recall and latency?

Sign in or go Pro to see the approach for this follow-up.

QWhy must nlist be fixed at build time?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.