Efficient Multivector Retrieval with Token-Aware Clustering and Hierarchical Indexing
Abstract: Multivector retrieval models achieve state-of-the-art effectiveness through fine-grained token-level representations, but their deployment incurs substantial computational and memory costs. Current solutions, based on the well-known k-means clustering algorithm, group similar vectors together to enable both effective compression and efficient retrieval. However, standard k-means scales poorly with the number of clusters and dataset size, and favours frequent tokens during training while underrepresenting rare, discriminative ones. In this work, we introduce TACHIOM, a multivector retrieval system that exploits token-level structure to significantly accelerate both clustering and retrieval. By accounting for tokens' distribution during centroid allocation, TACHIOM easily scales to millions of centroids, enabling highly accurate document scoring using only centroids, avoiding expensive token-level computation. TACHIOM combines a graph-based index over centroids with an optimized Product Quantization layout for efficient final scoring. Experiments on MS-MARCOv1 and LoTTE show that TACHIOM achieves up to $247\times$ faster clustering than k-means and up to $9.8\times$ retrieval speedup over state-of-the-art systems while maintaining comparable or superior effectiveness.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
What this paper is about
This paper introduces a faster and more memory‑friendly way to search through huge text collections using modern AI LLMs. The method is called TACHIOM. It speeds up two expensive steps:
- how to group many tiny word representations (called tokens) into “centroids” (think: representative buckets), and
- how to quickly find the best matching documents for a user’s query using those centroids.
The goal is to keep the strong accuracy of advanced systems like ColBERT (which compare query words to document words in detail), but make them fast enough and small enough to use in the real world.
The big questions the paper asks
- Can we cluster token vectors (the tiny number lists that represent each word in context) much faster than the usual k‑means method?
- Can we give more attention to rare but important words (like “mitochondria”) instead of letting very common words (like “the”) take over the clustering?
- Can we use only centroids (the “representatives”) to quickly gather promising documents, and then do a compact, efficient final check, without wasting time and memory?
- Will this be fast in practice and still accurate on standard search benchmarks?
How the method works (in everyday language)
Think of each document as a bag of smart word-pieces, each turned into a vector (a list of numbers). Searching means comparing the query’s word-pieces to the document’s word-pieces and adding up the best matches. That’s accurate, but slow if you do it for every word in every document.
This paper improves both the “grouping” and the “searching” parts.
1) Token‑Aware Clustering (TAC): smarter grouping
Normal k‑means clustering treats all vectors the same, so very frequent tokens hog most of the centroids. TAC does the opposite: it uses the identity and frequency of tokens to guide how many centroids each token type gets.
In simple terms: instead of mixing everything together, TAC first looks at which token the vector belongs to, then gives each token type a fair share of centroids based on:
- how often it appears (but with “damping” so common words don’t take everything),
- how much it varies in meaning across uses (its spread).
Then, it runs small, separate clustering jobs per token type (much easier to parallelize and much faster overall).
To make this concrete, TAC follows four steps:
- Tail handling: very rare tokens get at least a few centroids so they’re not ignored.
- Damped scoring: common tokens get less extra credit; tokens with more meaning variation get more centroids.
- Bounding: set sensible minimums and maximums so no token gets too few or too many centroids.
- Budget reconciliation: adjust the counts to hit the exact total number of centroids you want.
After assigning centroids, the method stores the “residual” for each token (the tiny difference between the token vector and its nearest centroid) in a compressed way using Product Quantization (PQ). Think of PQ like splitting a long number list into smaller chunks and replacing each chunk with a short code from a codebook.
Why this helps:
- Per‑token clustering is much faster (many small problems instead of one giant one).
- Rare, meaningful tokens get better representation, which improves search accuracy.
2) Hierarchical Indexing (TACHIOM): faster searching
TACHIOM uses the fine‑grained centroids created by TAC to speed up both stages of search:
- Gather stage (fast first pass): For each query token, it walks a graph built over the centroids (HNSW is like a shortcut map connecting similar centroids). It finds the nearest centroids, looks up which documents have tokens assigned to those centroids, and adds up a quick score per document using only centroid similarities. This stage never touches the heavy token vectors.
- Refine stage (accurate second pass): For the top candidate documents from the gather stage, it computes the full, accurate scores using both centroids and the compressed residuals. The paper reorganizes how these PQ distances are stored in memory so the computer can read them in big, neat chunks instead of many tiny scattered reads. This “cache‑friendly” layout makes the final scoring much faster.
Putting it simply:
- Stage 1 finds likely matches using only the “representatives.”
- Stage 2 double‑checks a small set of candidates thoroughly, but with compact, efficient data.
What they found and why it matters
- Clustering speed: TAC trains centroids up to 247x faster than standard k‑means. It can handle millions of centroids in a reasonable time, which older methods struggled with.
- Retrieval speed: TACHIOM makes end‑to‑end search up to 9.8x faster than strong recent systems (like EMVB, WARP, and IGP), while matching or beating their accuracy.
- Accuracy: Despite being faster, the method keeps high effectiveness on standard datasets (MS MARCO and LoTTE). Giving rare tokens more centroids helps keep the detailed meaning needed for good search results.
- Practicality: Because centroids are so good, the gather stage can skip heavy token‑level work, cutting both time and memory use.
Why this could be a big deal
- Real‑world use: High‑quality, fine‑grained search (like ColBERT) becomes much more practical for large collections and limited hardware.
- Cheaper and greener: Faster training and searching means lower costs and energy use.
- Better results where it counts: Rare, domain‑specific terms (often the most informative) get the attention they deserve, improving relevance.
- General potential: The idea of “token‑aware” processing and cache‑smart layouts could be applied to other retrieval systems and even bigger datasets.
The authors also released a Rust implementation, which helps others reproduce and build on these results.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
Below is a concise, actionable list of what remains missing, uncertain, or unexplored in the paper.
- Generalization beyond ColBERTv2: effectiveness of TAC/TACHIOM with other multivector encoders (e.g., ColBERT-X, XTR, late-interaction variants), different backbone LMs, and alternative tokenization schemes (WordPiece vs BPE, character/subword mixes).
- Cross-lingual and domain robustness: behavior on non-English, morphologically rich languages, and highly specialized domains with very different token frequency/variance profiles.
- Hyperparameter sensitivity of TAC: principled selection and robustness of p, t, floor (minimum centroids per token), and upper-bound parameters; impact on clustering time, memory, and retrieval effectiveness across datasets.
- Allocation function design: evaluation of alternatives to the proposed sqrt-frequency × variance weighting (e.g., IDF, entropy, mutual information, learned allocation via meta-optimization), and their effect on centroid distribution and retrieval quality.
- Rare/unseen tokens handling: impact of assigning 1–2 centroids to very rare tokens (risk of overfitting/underfitting), and strategy for tokens unseen during centroid training (e.g., incremental allocation, mapping to existing centroids) in dynamic corpora.
- Incremental updates and lifelong indexing: procedures to add documents or vocab items without full retraining of TAC centroids and HNSW; trade-offs in accuracy, time, and index consistency.
- Memory footprint and build-time analysis: quantitative breakdown of memory for millions of centroids (vectors + HNSW graph + inverted lists) and PQ codes; HNSW construction time and scaling characteristics with 2–4M nodes.
- Large-scale deployment: performance on web-scale corpora (billions of tokens) and in distributed or multi-node settings; throughput, tail latency (P95/P99), and contention under concurrent queries.
- Gather-phase recall guarantees: formal/empirical analysis of candidate recall when using centroid-only interactions versus token-level gather; failure modes where residuals dominate and centroid-only gather misses good candidates.
- Inverted list skew under TAC: distribution of posting-list lengths per centroid; impact on gather-phase cost and tail latencies; need for additional list-level pruning, balancing, or compression.
- Theoretical quality guarantees: absence of bounds relating TAC’s centroid-induced approximation to k-means distortion or to MaxSim score error; no analysis of convergence properties or iteration requirements of per-token k-means.
- Ablations on TAC iterations: effect of the number of iterations on clustering quality and retrieval performance; sensitivity to initialization strategies within per-token clustering.
- Residual normalization effects: impact of residual L2 normalization on reconstruction bias and MaxSim scoring; comparison to alternative normalizations or whitening; interaction with PQ codebooks.
- PQ design space: ablations over M (subspaces), codebook size (bits), OPQ/JMPQ vs standard PQ on TAC residuals; whether TAC enables higher compression ratios (≤16–24 bytes) without significant effectiveness loss.
- Cache-optimized distance table portability: efficacy of the proposed layout under AVX-512, ARM NEON, GPUs, and NUMA systems; memory bandwidth vs compute trade-offs and vectorization strategies on diverse hardware.
- Baseline comparability and training cost accounting: end-to-end training cost comparisons (e.g., JMPQ/OPQ training for baselines vs TAC-only); ensuring equalized budgets for a fair efficiency-effectiveness trade-off.
- Parameter tuning overhead: cost and robustness of grid-searching Kc, Kd, α, HNSW efSearch; methods for auto-tuning or adaptive control under changing query distributions.
- Graph parameter ablations: sensitivity to HNSW M and efConstruction on build time, memory, and search quality for multi-million centroid graphs.
- Scoring formulation details: impact of including/excluding IDF or per-token weights during gather/refine phases (ColBERT-style weighting) on effectiveness and speed; clarity on consistency with the original MaxSim scoring.
- Document length effects: impact of document length caps (e.g., 180 tokens) on indexing and retrieval; behavior for very long documents and passages aggregation strategies.
- Hybrid retrieval integration: how TACHIOM cooperates with strong sparse first-stage retrievers (e.g., SPLADE) in end-to-end pipelines; trade-offs in candidate overlap, latency, and effectiveness.
- Failure analysis: characterization of queries or token distributions where TAC allocation harms effectiveness (e.g., highly polysemous rare tokens, noisy tokens with high variance).
- Robustness to domain shift: how centroid allocations and graph search perform under temporal drift or when moving between domains without retraining.
- Energy and cost profiling: power/energy measurements for clustering, index building, and retrieval; comparisons to GPU-based k-means/IVF-PQ pipelines to guide practical deployment choices.
Practical Applications
Immediate Applications
Below are concrete, deployable applications that leverage the paper’s findings and system design as-is (using the released Rust implementation and standard multivector encoders like ColBERTv2).
- Sector: Web search and e-commerce — Lower-latency, higher-throughput multivector retrieval
- What: Replace standard k-means and gather/refine pipelines with TAC + TACHIOM to cut retrieval latency (up to ~9.8x in experiments) while preserving effectiveness for product and site search.
- Tools/products/workflows:
- Indexing: Run TAC to build millions of token-aware centroids; compress residuals with PQ (e.g., M=32, 8-bit); build HNSW over centroids.
- Serving: Centroid-only gather via HNSW; prune with CP; PQ-optimized refinement for MaxSim.
- Integration: Wrap the Rust implementation as a microservice; expose gRPC/REST for search.
- Assumptions/dependencies:
- Uses multivector encoders (e.g., ColBERTv2); offline index build required.
- HNSW memory for millions of centroids; PQ hyperparameters tuned per corpus.
- Tested on MS MARCO v1 and LoTTE; domain revalidation advised.
- Sector: Enterprise search and RAG for internal knowledge bases
- What: Speed up long-context document retrieval for assistants (e.g., chat over Confluence/Drive/SharePoint) with multivector reranking that favors rare, domain-specific terms.
- Tools/products/workflows:
- Use TAC to allocate centroids by token frequency/variance; deploy TACHIOM as a reranker behind sparse or dense first-stage retrieval.
- Integrate with LangChain/LlamaIndex via a retriever plugin.
- Assumptions/dependencies:
- Private corpora must be tokenized consistently with the chosen encoder.
- Index refresh is batch-oriented; frequent updates require periodic rebuilds.
- Sector: Scientific literature and patent search
- What: Improve recall for rare, discriminative terminology (e.g., biomedical concepts, IPC codes) by TAC’s token-aware centroid allocation.
- Tools/products/workflows:
- Batch ingest (PubMed, arXiv, USPTO); periodic TAC clustering; HNSW + PQ refinement at serve.
- Assumptions/dependencies:
- Domain drift may alter token statistics; schedule re-clustering; evaluate multilingual tokenizers when needed.
- Sector: Legal and financial research
- What: Faster case-law/filing retrieval with better handling of infrequent entities and citations via TAC; maintain interactivity under heavy loads.
- Tools/products/workflows:
- Deploy TACHIOM in a two-stage architecture; set aggressive CP pruning for responsiveness; use audit logs for retrieved evidence.
- Assumptions/dependencies:
- Sensitive data pipelines require access control; ensure PQ-residual storage complies with internal policies.
- Sector: Software development tools (code search)
- What: Token-aware clustering over code tokens (identifiers, APIs) to retrieve semantically similar snippets faster.
- Tools/products/workflows:
- Use a code-specialized multivector encoder; apply TAC per token; TACHIOM for search inside IDEs or code hosts.
- Assumptions/dependencies:
- Requires stable code tokenization; out-of-the-box results depend on encoder quality for code.
- Sector: Vector databases and IR engines (vendors/integrators)
- What: Offer a “token-aware multivector index” option (TAC for centroid training + HNSW gather + PQ-optimized refinement) as a built-in retrieval plan.
- Tools/products/workflows:
- Add a TACHIOM backend alongside HNSW/IVF; expose knobs for centroid budget, CP threshold, PQ layout.
- Assumptions/dependencies:
- Expects multi-vector embeddings; single-vector customers need encoder upgrades.
- Sector: Academia and benchmarking
- What: Faster experimentation with multivector methods; cluster hundreds of millions of vectors into millions of centroids within hours to test hypotheses.
- Tools/products/workflows:
- Use the open-source Rust repo; reproduce baselines; ablate centroid budgets; test on new corpora.
- Assumptions/dependencies:
- CPU-only pipelines demonstrated; GPU acceleration optional but not required.
- Sector: Cost/energy optimization (cross-sector)
- What: Reduce compute cost and carbon footprint by using centroid-only gathering and PQ-optimized refinement instead of exhaustive token interactions.
- Tools/products/workflows:
- Monitor query-time CPU cycles and energy; select lower Kc/Kd for business-acceptable effectiveness.
- Assumptions/dependencies:
- Trade-offs must be validated for each application’s relevance metrics.
- Sector: Personal search (daily life)
- What: Self-hosted, fast search over emails/notes/wiki with multivector quality on a laptop/desktop CPU.
- Tools/products/workflows:
- Periodic TAC clustering; small HNSW graph over centroids; bind Rust to a local app (Electron/Tauri).
- Assumptions/dependencies:
- Storage for PQ codes and centroids; initial index build time; privacy-safe local embeddings.
- Sector: News/media search and monitoring
- What: Low-latency retrieval across large news archives; better handling of niche entities and novel terms.
- Tools/products/workflows:
- Nightly re-index with TAC; TACHIOM serving; partial re-encode for fresh content windows.
- Assumptions/dependencies:
- Near-real-time updates may require hybrid batch+micro-batch indexing.
- Sector: Healthcare (clinical text retrieval)
- What: Retrieve patient notes/literature passages with rare clinical terms prioritized by TAC; enable faster decision support.
- Tools/products/workflows:
- Domain encoder for clinical text; privacy-preserving on-prem deployment; audit trails for retrievals.
- Assumptions/dependencies:
- Regulatory constraints (HIPAA/GDPR); rigorous validation for clinical safety.
- Sector: Education (learning platforms, question banks)
- What: Improve question-to-content matching, emphasizing rare concepts in curricula.
- Tools/products/workflows:
- TAC-based centroids trained on course materials; TACHIOM search for practice and remediation content.
- Assumptions/dependencies:
- Content updates scheduled; ensure alignment with pedagogical relevance metrics.
Long-Term Applications
These directions are promising but require additional research, engineering, or validation beyond the paper’s immediate scope.
- Sector: Dynamic/online indexing for streaming data
- What: Incremental TAC (per-token) updates and online HNSW maintenance for near-real-time ingestion (news feeds, incident logs).
- Dependencies/assumptions:
- Requires algorithms for online centroid reallocation and residuals re-quantization; consistency under churn.
- Sector: Cross-encoder generalization and multilingual support
- What: Apply TAC to alternative multivector encoders (XTR, ColBERT variants) and tokenizers (subword, syllable, character) across languages.
- Dependencies/assumptions:
- Token identity must correlate with embedding distributions; weighting scheme may need re-learning.
- Sector: Mobile/on-device RAG and private search
- What: Deploy TACHIOM with smaller centroid budgets and aggressive compression for on-device assistants that run offline.
- Dependencies/assumptions:
- Memory constraints stringent; compile Rust to WASM/ARM; evaluate battery and thermal envelopes.
- Sector: Multimodal retrieval (vision/text/audio)
- What: Extend token-aware clustering to patch/frame-level “tokens” (e.g., ViT patches) for fast cross-modal search.
- Dependencies/assumptions:
- Requires a principled “token identity” for non-text modalities; per-token variance measures may differ.
- Sector: Learned allocation and supervised compression
- What: Replace square-root frequency and variance heuristics with learned allocation (e.g., reinforcement, meta-learning) and integrate OPQ/JMPQ training jointly with encoders.
- Dependencies/assumptions:
- Additional training cost and labeled data; careful generalization across domains.
- Sector: Federated and privacy-preserving indexing
- What: Apply TAC per-tenant or per-site; aggregate centroids securely; serve TACHIOM over encrypted or differentially private residuals.
- Dependencies/assumptions:
- Protocols for secure centroid sharing; accuracy-energy-privacy trade-offs.
- Sector: Database-native IR
- What: Integrate TACHIOM layouts (centroid inverted lists + PQ micro-blocks) into columnar or hybrid DBMS for unified SQL+IR workloads.
- Dependencies/assumptions:
- Storage engine changes for PQ distance tables and HNSW management; cost-based query planning.
- Sector: Personalized retrieval and adaptive weighting
- What: Adjust per-user centroid allocation or query-time CP thresholds using feedback/telemetry to personalize latency–quality trade-offs.
- Dependencies/assumptions:
- Feedback loops and privacy safeguards; online learning of allocation weights.
- Sector: Energy-aware search policy and procurement
- What: Establish benchmarks and procurement guidelines for public-sector search platforms favoring energy-efficient multivector retrieval (using centroid-only gather).
- Dependencies/assumptions:
- Standardized energy metrics; field trials on government portals.
- Sector: Content moderation and safety tools
- What: Rapid retrieval of contextually similar harmful content using token-aware centroids emphasizing rare/novel phrases.
- Dependencies/assumptions:
- Robustness to adversarial paraphrases; governance for false positives/negatives.
- Sector: Large-scale cross-collection search (data lakes)
- What: Hierarchical, token-aware indexing across heterogeneous corpora; route queries to sub-indices by token distributions for better load balancing and recall.
- Dependencies/assumptions:
- Index orchestration layer; policies for shard-level centroid budgets and rebalancing.
Notes on Key Assumptions and Dependencies (cross-cutting)
- Embedding model: The method presumes multivector encoders (e.g., ColBERTv2) that expose token-level vectors; single-vector dense models require architectural changes.
- Token identity: TAC’s gains rely on stable token distributions and meaningful per-token variance; dramatically different tokenization schemes may need retuning.
- Index build vs. update: TAC excels at batch clustering; frequent, fine-grained document updates will need incremental strategies not covered by the paper.
- Hardware: Results were measured on CPUs; HNSW search and PQ refinement are CPU-friendly. GPU paths may yield further gains but require engineering.
- Memory/storage: Millions of centroids + inverted lists + PQ residuals require careful memory budgeting; choose centroid budgets per workload.
- Hyperparameters: Kc, Kd, CP threshold α, PQ settings (M, bits), and HNSW parameters (M, efConstruction/efSearch) must be tuned to domain metrics.
- Generalization: Effectiveness and speedups were shown on MS MARCO v1 and LoTTE; replication on other corpora and languages is recommended before production deployment.
Glossary
- Cache-optimized PQ layout: A data layout for Product Quantization distances designed to improve cache locality and memory access patterns during scoring. "a cache-optimized PQ lay- out for efficient refinement."
- Candidates Pruning (CP): A strategy to reduce the number of candidate documents by filtering based on partial scores. "We also apply adaptive filtering to further reduce the candidate set, adopting the Candidates Pruning (CP) strategy proposed in [19], regulated by a parameter a."
- Centroid interaction: Computing interactions between query tokens and cluster centroids to approximate token-level matching. "WARP [26] combined PLAID's centroid interaction with XTR's lightweight architecture [16];"
- Coarse quantizer: A first-level quantizer (set of centroids) used to coarsely partition the embedding space before finer residual quantization. "Both phases critically depend on a coarse quantizer-a set of cen- troid vectors that approximate the token embedding space."
- ColBERT: A multivector IR model using late interaction between query and document token embeddings. "Within this landscape, multivector models, such as ColBERT [14, 25], have emerged as a gold standard for effectiveness."
- COLBERTv2: An improved ColBERT variant that compresses residuals relative to centroids for efficient multivector retrieval. "We use COLBERTv2 [25] as the encoder with a maximum of 180 tokens"
- Damped Scoring: A TAC phase that assigns centroid budgets to tokens using frequency-damped, variance-aware weights. "Phase 2: Damped Scoring."
- Distance tables: Precomputed lookup tables of distances between query tokens and PQ centroids for each PQ subspace. "Distance Table Layout: PQ requires precomputing distance tables between query tokens and PQ centroids for each PQ subspace."
- efc: The HNSw (construction) parameter controlling graph construction complexity/quality. "The HNSw graphs over centroids are built with M = 32 neighbors and efc = 1500."
- efs: The HNSw (search) parameter controlling the breadth of exploration during query time. "with HNSw search parameter efs = 2Kc."
- Gather Phase: The first stage that selects candidate documents using fast centroid-level interactions. "Gather Phase: Centroid-based Document Scoring."
- Graph index: A proximity-graph-based data structure over centroids to accelerate nearest-neighbor search. "IGP [1] proposed building a graph index on the set of centroids to avoid exhaustive centroids scoring."
- HNSw (Hierarchical Navigable Small World) graph: A multilayer proximity graph enabling efficient approximate nearest neighbor search. "We build an HNSw [18] graph over the centroid set;"
- Inertia: The k-means clustering objective equivalent to within-cluster sum of squares. "K-means aims to find a set of clusters C = {C1, ... , Ck} that partitions the dataset and minimizes the Within-Cluster Sum of Squares (WCSS) or Inertia, i.e .:"
- Inverse Document Frequency (IDF): A weighting scheme favoring rare terms, adapted here to guide centroid allocation. "Drawing from classic Information Retrieval literature, where Inverse Document Frequency (IDF) has long been employed to favor rare, discriminative terms [22, 23]"
- Inverted-file filtering: Using inverted index structures over clustered embeddings to quickly filter candidates. "PLAID [24] extended this framework with centroid interaction and inverted-file filter- ing over clustered token embeddings for efficient retrieval."
- Inverted list: For each centroid, the list of document IDs of tokens assigned to that centroid. "each centroid ci maintains an inverted list Li containing the document IDs of all tokens assigned to ci."
- JMPQ: A supervised PQ variant that jointly optimizes centroids, PQ, and the query encoder. "EMVB, conversely, relies on computationally expensive PQ variants, namely JMPQ [7]-a supervised method that jointly trains centroids, PQ, and the query encoder-on Ms MARCO-v1"
- Late interaction: A scoring paradigm where every query token interacts with every document token. "computing relevance via late interaction, i.e., allowing every query token to interact with every document token,"
- Macro-blocks: Top-level blocks in the PQ distance table layout, each corresponding to a PQ subspace. "* Macro-blocks: indexed by PQ subspace (M blocks for M subspaces);"
- MaxSim: The late-interaction aggregation that takes, for each query token, the maximum similarity over document tokens and sums across query tokens. "full MaxSim scores are computed only for the selected candidates."
- Micro-blocks: Small contiguous blocks in the PQ distance table holding distances for all query tokens to a fixed PQ centroid within a subspace. "* Query token micro-blocks: containing nq consecutive dis- tances between each query token and the same PQ centroid on that subspace."
- MRR@10: Mean Reciprocal Rank at cutoff 10, an effectiveness metric for retrieval. "We evaluate the retrieval results using the standard metrics for each dataset: MRR@10 for Ms MARCO-v1 and Success@5 for LoTTE."
- OPQ (Optimized Product Quantization): A PQ variant that rotates the space before subquantization to reduce quantization error. "and OPQ [10] on LoTTE."
- Product Quantization (PQ): A vector quantization technique that decomposes vectors into subspaces and quantizes each with its own codebook. "Product Quantization 12."
- Proximity graph: A graph connecting nearby points to support efficient nearest neighbor search. "combines an HNSw proximity graph over centroids for efficient gathering"
- Refine Phase: The second stage that computes full scores using centroids and PQ-compressed residuals for top candidates. "Refine Phase: PQ-Optimized MaxSim Computation."
- RerankIndex: An index implementation used to rerank retrieved candidates under controlled settings. "using the RerankIndex with all optimizations disabled-"
- Residual vector: The difference between a token embedding and its assigned centroid, used for fine-grained reconstruction. "compress the residuals, i.e., the difference between each token vector in the dataset and its assigned centroid, using PQ [12]."
- Scalar Quantization: A quantization approach that independently quantizes each vector component to a small number of bits. "with 2 bits per component for the Scalar Quantization employed by WARP and IGP."
- SIMD vectorization: Parallelizing computations using Single Instruction Multiple Data CPU instructions. "We adopt specialized data layouts optimized for cache locality and SIMD vectorization."
- Success@5: A top-k success metric (at 5) used for retrieval evaluation on LoTTE. "We evaluate the retrieval results using the standard metrics for each dataset: MRR@10 for Ms MARCO-v1 and Success@5 for LoTTE."
- TACHIOM: The proposed system combining Token-Aware Clustering and hierarchical indexing for efficient multivector retrieval. "we introduce TACHIOM, a multivector re- trieval system that exploits token-level structure to significantly accelerate both clustering and retrieval."
- Token-Aware Clustering (TAC): A clustering method that allocates centroids per token type based on frequency and variance to improve speed and retrieval quality. "Token-Aware Clustering (TAC) explicitly exploits the token structure of multivec- tor representations."
- Vector Quantization (VQ): A family of methods that approximates vectors by nearest centroids and encodes residuals for compression. "Vector Quantization (VQ) techniques, like, for instance, Product Quantization 12."
- Within-Cluster Sum of Squares (WCSS): The sum of squared distances from points to their cluster centroids; the standard k-means objective. "K-means aims to find a set of clusters C = {C1, ... , Ck} that partitions the dataset and minimizes the Within-Cluster Sum of Squares (WCSS) or Inertia, i.e .:"
Collections
Sign up for free to add this paper to one or more collections.