Retrieval's bottleneck is moving from finding to selecting
emil_sorensen
31 points
2 comments
October 26, 2026
Related Discussions
Found 5 related stories in 106.7ms across 10,677 title embeddings via pgvector HNSW
- Evals Are the Next Bottleneck ssatia · 14 pts · August 20, 2026 · 54% similar
- Benchmarking retrieval for agents on messy real-world company knowledge emil_sorensen · 25 pts · October 02, 2026 · 53% similar
- Understanding is the new bottleneck sebg · 270 pts · August 13, 2026 · 49% similar
- Choosing the Right AI Agent Memory Strategy: A Decision-Tree Approach eigenBasis · 12 pts · July 11, 2026 · 46% similar
- AI recursive self-improvement might not come so quickly after all dgellow · 69 pts · September 13, 2026 · 46% similar
Discussion Highlights (2 comments)
emil_sorensen
OP here! Happy to jump in to answer any questions. :)
theybash
I found 2 things that work for me. First, something I call density RAG: the agent calls it with multiple queries and gets back a semantic "heatmap", a table with chunks as rows, queries as columns and similarity scores in the cells. From this, the agent chooses which chunks to retrieve. Second, for the noise problem, passing the chunks through a decision model usually cuts it down. This is just my experience, I haven't benchmarked it yet.