Using LLMs to measure what LLMs cost and why smaller models aren't always cheaper
Summary
Using smaller, cheaper LLMs can increase total workflow costs due to hidden expenses like review time and error correction, highlighting the need for comprehensive cost tracking.
Similar Articles
10 Ways To Reduce Your LLM API Costs
A practical guide listing 10 strategies to reduce costs when using LLM APIs, including model selection, prompt caching, batch processing, and monitoring expenses.
I think “use fewer tokens” is too shallow as LLM cost advice
This article argues that common LLM cost advice focusing on token reduction is too shallow, and that the more impactful strategy in production is to route different workflow steps to different models rather than using a single default model.
We optimize LLM costs before we ask what the AI is for
An AI consultant reflects on how teams optimize LLM costs without questioning whether the task needs a model at all, and advocates measuring cost per successful outcome rather than per token.
@LangChain: Reining in LLM spend gets harder once your team has started using multiple agents calling multiple models. Without the …
The article provides a walkthrough on setting and enforcing cost controls using LangSmith LLM Gateway to manage expenses when using multiple LLM agents.
The Embedder's Dilemma: LLMs Are Better, but at What Cost?
This paper presents a cost-aware comparison of LLMs versus dedicated embedding models across 37 tasks, finding that the best LLM and embedding model are nearly tied on aggregate performance but LLMs are up to 1,431x more expensive and slower, leading to a recommended division of labor.