Searcharxiv⌕ Search

arXiv · 2610.29689

WaRP: Workload-Aware Request Planning for Vector Retrieval on Object Storage

Abstract

Modern vector search systems keep payload vectors in cloud object storage and only a compact routing index on fast local storage, typically using cluster-based ANN indexes. This design inherits a problem existing systems do not address. On object storage, small Range-GETs have latency dominated by fixed per-request overhead and are billed per request. Existing readers either issue one request per probed cluster, or coalesce adjacent ranges with hand-tuned gap or span thresholds that do not transfer across datasets or query workloads. We formulate the grouping of probed-cluster byte intervals into object-store requests as a global per-query optimization problem and present WaRP, a workload-aware request planner that solves it efficiently. Given the sorted byte intervals, a limit on the number of requests per query, and an estimate of how many object-store requests from one query can proceed concurrently under the target serving configuration, WaRP searches for a merge plan that minimizes a concurrency-aware latency surrogate while satisfying the request limit. Using an optimized dynamic program and adaptive frontier search, WaRP returns a plan within $(1{+}ε)$ of the optimum, with per-query planning overhead under $10$ms even in the most demanding tested settings. A lightweight offline reordering pass further improves request mergeability without changing the semantics of ANN search. We implement WaRP inside Lance's I/O scheduler and evaluate it on AWS S3. We build IVFPQ indexes on seven datasets, including SIFT100M and DEEP100M at the 100M-vector scale. WaRP + Reorder improves QPS by $1.09--3.48\times$ and reduces GETs by $2.12--5.19\times$ relative to Lance, while preserving Lance's recall.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Ruipeng Wan, Xinyu Zeng, Yiming Qiao, Huanchen Zhang. 2026-10-21. WaRP: Workload-Aware Request Planning for Vector Retrieval on Object Storage. https://arxiv.org/abs/2610.29689

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

Resilience for Regular Path Queries: Towards a Complexity Classification

The resilience problem for a query and an input set or bag database is to compute the minimum number of facts to remove from the database to make the query false. In this paper, we study how to compute the resilience of Regular Path Queries (RPQs) over graph databases. Our goal is to characterize the regular languages L for which it is tractable to compute the resilience of the existentially-quantified RPQ built from L. We show that computing the resilience in this sense is tractable (even in combined complexity) for all RPQs defined from so-called local languages. By contrast, we show hardness in data complexity for RPQs defined from the following language classes (after reducing the languages to eliminate redundant words): all finite languages featuring a word containing a repeated letter, and all languages featuring a specific kind of counterexample to being local (which we call four-legged languages). The latter include in particular all languages that are not star-free. Our results also imply a dichotomy on all languages with a so-called neutral letter. We last show tractability for some classes of non-local languages, namely the so-called bipartite chain languages and one-dangling languages, and highlight some remaining obstacles towards a full dichotomy.

cs.DB↗

Efficient Path Query Processing in Relational Database Systems

Path queries are crucial for property graphs, and there is growing interest in queries that combine regular expressions over labels with constraints on property values of vertices and edges. Efficient evaluation of such general path queries requires that intermediate results be eliminated early when there is no possible completion to a full result path. Neither state-of-the-art (SOA) graph DBMS nor relational DBMS currently can do this effectively for a large class of queries. We show that this problem can be addressed by giving a relational optimizer ``a little help'' by specifying early filtering opportunities explicitly in the query. To this end, we propose ReCAP, an abstraction that greatly simplifies the implementation of early filtering techniques for any type of property constraint for which such early filtering can be derived. No matter how complex the constraint, one only needs to implement (1) an NFA-style state transition function and (2) a handful of functions that mirror those needed for user-defined aggregates. We show that when using ReCAP, a standard relational DBMS like DuckDB can effectively push property constraints deep into the query plan, beating the SOA graph and relational DBMS by a factor up to 400,000 over a variety of queries and input graphs.

cs.DB↗

Ozone: A Unified Platform for Transportation Research

Transportation research increasingly depends on heterogeneous data from roadside cameras, UAV imagery, LiDAR, and in-vehicle sensors. Differences in data representations, model interfaces, and evaluation protocols complicate cross-dataset benchmarking and reproducibility. We present Ozone, a unified transportation research platform organized around Hardware, Data, Model, and Evaluation layers, with a Prototype layer supporting deployment-oriented applications. Its data layer links vehicle trajectories, traffic conflicts, reconstructed crashes, and digital-twin maps through a shared trajectory schema. The source inventory spans 19 trajectory datasets recorded at 59 sites in eight countries, with completed converters for 12 sources and adaptation ongoing for seven. The converters align coordinate systems, object classes, oriented bounding boxes, and kinematic fields. A shared implementation of surrogate safety measures supports conflict extraction, while map and motion constraints link crash reports to reconstructed trajectories. CARLA digital-twin maps and SUMO traffic logic connect these records to simulation, model development, and evaluation. Validation on 500 vehicles from four datasets reports mean position, heading, and speed errors below 0.15 m, 2.5°, and 0.3 m/s. A workflow study reports an 85 % reduction in experiment setup time. Case studies demonstrate human-factor experiments and automated-driving safety testing, while the model interfaces support traffic modeling and world-model research. The source code and datasets are publicly available.

cs.DB↗