Skip to main content
Software Engineering Daily

DeepMind’s RAG System with Animesh Chatterji and Ivan Solovyev

37 min episode · 2 min read
·
Animesh Chatterji

Episode

37 min

Read time

2 min

Topics

Relationships, Investing, Fundraising & VC

AI-Generated Summary

Key Takeaways

  • Embedding model quality drives 80% of RAG outcomes: Configuration tuning — chunk size, overlap, re-ranking — accounts for roughly 20% of retrieval quality. The embedding model itself determines the majority of results. DeepMind recommends developers first swap in Gemini's embedding model on their existing pipeline before migrating fully to FileSearch, as this single change yields the largest quality improvement.
  • Simplified pricing model: pay only for indexing and tokens: FileSearch eliminates separate charges for storage, infrastructure, and inference. Developers pay once at upload time for embedding and indexing, then pay only for tokens during queries. For large enterprise datasets, this structure reduces costs substantially compared to multi-component billing models common across competing RAG pipeline providers.
  • Optimal retrieval sits at low double-digit chunk counts: FileSearch returns roughly five chunks per query by default, a threshold validated across legal document search and code completion use cases with partners. The system applies a quality score cutoff to filter low-relevance chunks rather than re-ranking, since re-ranking added complexity without measurable retrieval quality improvement in internal evaluations.
  • Fine-tuning embedding models becomes obsolete within six months: DeepMind's general recommendation discourages fine-tuning because base model improvements — typically 15% gains across benchmarks — arrive faster than custom fine-tuning cycles complete. The only justified exception is a highly niche dataset that major labs are unlikely to address. Developers should factor this deprecation timeline into any fine-tuning investment decision.
  • Matryoshka embedding representation enables storage-quality trade-offs: Gemini's latest embedding model encodes vectors so that the leading dimensions carry the highest semantic density. Developers can truncate a 3,000-dimension vector at any point and retain a usable representation, reducing storage costs at a controlled quality cost. FileSearch may expose this truncation threshold as a configurable API parameter in a future release.

What It Covers

Google DeepMind engineers Animesh Chatterji and Ivan Solovyev explain how FileSearch, a fully managed RAG tool built into the Gemini API, abstracts away vector databases, chunking, and indexing infrastructure, while covering embedding model improvements, pricing simplification, retrieval quality trade-offs, and the road toward multimodal retrieval support.

Key Questions Answered

  • Embedding model quality drives 80% of RAG outcomes: Configuration tuning — chunk size, overlap, re-ranking — accounts for roughly 20% of retrieval quality. The embedding model itself determines the majority of results. DeepMind recommends developers first swap in Gemini's embedding model on their existing pipeline before migrating fully to FileSearch, as this single change yields the largest quality improvement.
  • Simplified pricing model: pay only for indexing and tokens: FileSearch eliminates separate charges for storage, infrastructure, and inference. Developers pay once at upload time for embedding and indexing, then pay only for tokens during queries. For large enterprise datasets, this structure reduces costs substantially compared to multi-component billing models common across competing RAG pipeline providers.
  • Optimal retrieval sits at low double-digit chunk counts: FileSearch returns roughly five chunks per query by default, a threshold validated across legal document search and code completion use cases with partners. The system applies a quality score cutoff to filter low-relevance chunks rather than re-ranking, since re-ranking added complexity without measurable retrieval quality improvement in internal evaluations.
  • Fine-tuning embedding models becomes obsolete within six months: DeepMind's general recommendation discourages fine-tuning because base model improvements — typically 15% gains across benchmarks — arrive faster than custom fine-tuning cycles complete. The only justified exception is a highly niche dataset that major labs are unlikely to address. Developers should factor this deprecation timeline into any fine-tuning investment decision.
  • Matryoshka embedding representation enables storage-quality trade-offs: Gemini's latest embedding model encodes vectors so that the leading dimensions carry the highest semantic density. Developers can truncate a 3,000-dimension vector at any point and retain a usable representation, reducing storage costs at a controlled quality cost. FileSearch may expose this truncation threshold as a configurable API parameter in a future release.

Notable Moment

The team pushed back on the widespread claim that agents make RAG obsolete, arguing the framing misunderstands what RAG is. They noted RAG is itself a tool given to agents, and that personalization features at DeepMind are now being implemented using RAG-style chunk retrieval mechanisms.

Know someone who'd find this useful?

Episode Transcript

Retrieval Augmented Generation, or RAG, has become a foundational approach to building production AI systems. However, deploying RAG in practice can be complex and costly. Developers typically have to manage vector databases, chunking strategies, embedding models, and indexing infrastructure. Designing effective RAG systems is also a moving target, as techniques and best practices evolve in step with rapidly advancing language models. Google DeepMind recently released the FileSearch tool, a fully managed RAG system built directly into the Gemini API. FileSearch abstracts away the retrieval pipeline, allowing developers to upload documents, code, and other text data, automatically generate embeddings, and query their knowledge base. We wanted to understand how the DeepMind team designed a general purpose reg system that maintains high retrieval quality. Animesh Chatterjee is a software engineer at Google DeepMind, and Ivan Solavyev is a product manager at DeepMind, and they worked on the file search tool. They joined the podcast with Sean Falconer to discuss the evolution of RAG, why simplicity and pricing transparency matter, how embedding models have improved retrieval quality, the trade offs between configurability and ease of use, and what's next for multimodal retrieval across text, images, and beyond. This episode is hosted by Sean Falconer. Check the show notes for more information on Sean's work and where to find him. Yvonne and Animesh, welcome to the show. Thank you so much. Pleasure to be here. Awesome. Well, why don't we so there you know, we have two guests today just so everyone can kinda learn whose voice is who. Why don't we start off with Ivan, we'll start with you. You know, who are you and what do you do? Yeah. My name is Ivan. I'm product manager for file search on Gemini API. Great. And, Animesh, you? Hi. I'm Animesh. I'm the engineering lead on file search. Awesome. Well, thanks both for being here. So, you know, we're talking about this product, which you you mentioned to your file, the FHIR search tool for Gemini APIs. And before we get too deep into, I think, sort of some general things around with AI, RAG, agents, and so on, Can you talk a little bit about, you know, what the file search tool is and what problem it tries to address? Maybe, Yvonne, you can take that. Yeah. Absolutely. So file search tool, first of all, is a integrated rack solution that makes it super easy for you to take loads and loads of data, text, PDFs, codes, whatever you have uploaded into Gemini and start asking questions about your data. There are plenty of rack pipelines available on the market, like we have vertex rack engine, and there are other providers who do support this feature. So it's nothing you. And what we focused on in file search in particular is accessibility and simplicity of use. We made some opinionated decisions, we removed a lot of complexity in terms of configuration setup, you don't need to set up your database, you don't need …

Get the full transcript (7,417 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Software Engineering Daily transcripts →

You just read a 3-minute summary of a 34-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • FileSearchRecommendedBy guest

    by Google DeepMind

    Google DeepMind engineers Animesh Chatterji and Ivan Solovyev explain how FileSearch, a fully managed RAG tool built into the Gemini API, abstracts away vector databases, chunking, and indexing infrastructure.
  • SPONSORS: Recall.ai
  • Gemini APIRecommendedBy guest

    by Google DeepMind

    FileSearch, a fully managed RAG tool built into the Gemini API, abstracts away vector databases, chunking, and indexing infrastructure.

company

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Investing & Markets Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime