The FAISS-plus-BM25 retrieval in this writeup does address vocabulary mismatch, but the agent loop around it ran at over 213 seconds a step on CPU, and that figure decided the deployment, not the retrieval design.
Reality
- Evidence34
- Adoption14
- Hype gap+42
- Incentives38
- Confidence56
The provider cache discounts a repeated prefix, and the worst case is bounded arithmetic. The semantic cache deletes the call outright, but a miss there means a wrong answer, not a rounding error, so the threshold sweep matters more than the hit rate.
Reality
- Evidence46
- Adoption
- Insufficient
- Hype gap+32
- Incentives34
- Confidence54
A dev.to writeup drops vector stores for a SQLite table with tag and timestamp columns. Its own numbers put the practical ceiling at a million rows, not a hundred million.
Reality
- Evidence24
- Adoption
- Insufficient
- Hype gap+42
- Incentives
- Insufficient
- Confidence33
A developer wired runtime schema introspection, vector field matching and a local LLM repair loop into Odoo 17, then published the failure list. The failures define the boundary.
Reality
- Evidence40
- Adoption
- Insufficient
- Hype gap−10
- Incentives38
- Confidence48
A dev.to walkthrough wires chokidar, tree-sitter, Qdrant and an MCP server into a code search stack. Every part is off the shelf; the unresolved work is reindexing and retrieval quality.
Reality
- Evidence27
- Adoption
- Insufficient
- Hype gap+42
- Incentives40
- Confidence40
HNSW indexing runs inside the SQL engine, so there is no second service and no network hop. There is also no index persistence unless you turn on an experimental flag.
Reality
- Evidence58
- Adoption
- Insufficient
- Hype gap+12
- Incentives
- Insufficient
- Confidence52