live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
benchmarkBENCHMARK AUDIT

LinePG’s 44.76× SIFT throughput gain comes with better recall—not an equal-recall shortcut

A new line-query vector index rewires HNSW with bounded pair edges, but its strongest headline comparison is also the one readers should interpret most carefully.

By The Benchmark Desk· Oct 29, 2026the quick take — two AI hosts go live when you do

The result that matters

LinePG reports 613.11 queries per second at 99.58% Recall@10 on the full 1-million-vector SIFT dataset. The strongest tested direct-search configuration over the original HNSW graph reaches 13.70 QPS at 98.93% recall. That is a 44.76× throughput advantage while also improving recall, rather than a speedup interpolated at an identical quality point.

The distinction matters because line nearest-neighbor search is not ordinary point search. Each query is an infinite line defined by two endpoints; points close to that line can sit in regions that are far apart from one another. A graph built only around point-to-point proximity can therefore settle into one region and miss another. LinePG keeps HNSW’s total degree limit at 32 but reserves up to four selected “pair edges” per point to bridge those separated regions.

What was actually tested

The paper evaluates six full datasets: YaleB (15,624 vectors, 252 queries), CelebA (60,000, 1,000), FFHQ (70,000, 1,000), Multi-PIE (246,012, 6,474), SIFT (1 million, 10,000) and GIST (1 million, 10,000). It compares LinePG with direct line-distance search on HNSW, a quadratic-dimension lifting method, brute-force scanning and—on 512-vector subsets only—a theoretical line-search implementation.

At recall of at least 99%, LinePG’s full-dataset QPS gain over direct search ranges from 1.55× to 4.23× for top-10 retrieval on the four datasets where both methods crossed that threshold. Direct search did not reach 99% on full SIFT or GIST for top-10 within the tested range. For top-100, where all six comparisons clear 99%, the reported gain ranges from 1.44× to 2.44×.

The index-cost result is less dramatic but operationally useful. Across the full datasets, LinePG occupies 1.000× to 1.046× the storage of direct HNSW. On GIST, it adds 255.680 seconds of enhancement work to a 2,271.748-second HNSW build, producing a 2,527.428-second total.

The boundary on the claim

This is a single-paper evaluation on one CentOS server with an Intel Xeon Silver 4215, 128GB of memory, C++17 and single-threaded search. SIFT and GIST line queries are synthetically formed by pairing released point queries; they are not observed production line-query logs. The arXiv record links the paper but no public code repository, so the results are not yet independently reproducible from a packaged artifact.

The strongest conclusion is therefore narrower than “vector search is 44× faster.” Pair-edge augmentation appears to repair a specific failure mode of ordinary proximity graphs for line queries, and it does so without relaxing the degree bound. Independent code and non-image workloads are the next evidence needed.

Filed by The Benchmark Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.