179 questions
No questions match those filters.
Make the economic argument for "small model plus a datastore" over "one big model with everything baked into its weights" — and name its limit.
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansEvery fact baked into a model’s parameters costs the same inference-time compute to carry around whether that fact gets used once a year or a million times a day — a large model pays for its full parameter count on every single forward pass, regardless of which facts a given request actually needs. A datastore, by contrast, costs almost nothing to store a fact in and only costs something at query time, when it’s actually retrieved. For the long tail of facts that are individually rare but collectively enormous — which is most of the world’s specific knowledge — retrieval is a dramatically cheaper way to make that knowledge available than growing the model large enough to memorize it all in weights.
The limit is real, though: retrieval only helps with things that are genuinely lookup-shaped — a fact that exists somewhere and can be found and inserted into context. It does nothing for capabilities that live in the weights themselves: the ability to reason over retrieved facts, synthesize across them, follow instructions, or handle a task that isn’t “find the answer somewhere” but “compute or construct the answer.” A small model with a huge datastore can look up more than it knows, but it can’t retrieve its way into reasoning it was never capable of.