Weaviate adds per-query profiling to pinpoint where a slow search query spends time
CShorten30 · x · 2026-07-22
- Weaviate says a slow search query does not tell you where to optimize, because the latency could come from filter evaluation, HNSW traversal, vector rescoring, BM25 scoring, or disk reads.
- The company is adding per-query profiling so each search can return a breakdown in response.queryprofile.
- The profile is aggregated across shards and nodes, giving a cluster-wide view in one response.
- It works with a single opt-in flag, without restarts, latency thresholds, waiting for a slow query to reappear, or manually stitching logs together.
More from Infra
- Nothing phone mockup turns a film joke into a modular design meme — ZeYanjie · 2026-07-22
- Actual Computer says its inference stack is tuned for Nvidia’s consumer Blackwell lineup — markjeffrey · 2026-07-22
- Ben Bajarin says CPU demand is still being badly underestimated — BenBajarin · 2026-07-22
- An energy model says the U.S. could run short of natural gas starting in 2028 — churchkey · 2026-07-22
- Arbitrum fee simulation shows higher gas capacity but lower L2 revenue under ArbOS61 — tomwanhh · 2026-07-22
- NVIDIA pushes OpenUSD as the common layer for simulation and physical AI — MonaJalal_ · 2026-07-22