Asked about Evals in the loop
How do you stop evals becoming expensive to run?
An answer that works
Run a small fast subset on every push and the full set nightly or before release. Cache results for unchanged inputs, and report the cost of the eval run itself so the trade-off stays visible.
Reading an answer is not being able to give one. The section that teaches this is Evals in the loop, 6 hours of Evaluation.
Learn this properlyAlso asked about Evaluation
What is an eval?Why can you not just use unit tests?How would you start evaluating an existing feature with no evals?You join a team with an LLM feature and no evals. What do you do in the first week?Why note only the first failure in a trace?Why binary judges rather than a one to five scale?Where do eval cases come from?Why split an eval set into train and test?
All 24 questions on Evaluation