This website uses cookies to ensure you get the best experience.
Learn more.
A RAG experiment improves answer correctness but doubles latency beyond the service target. What should the team do?
Published
- Hide slow examples from the evaluation report.
- Convert milliseconds to seconds and claim latency decreased.
- Evaluate the quality-latency tradeoff against explicit acceptance criteria.
- Ship automatically because correctness is the only possible requirement.
Comments — 0
Sign in to comment