How do you reduce token cost in a production RAG app?
PICTURE THIS: A SENTENCE BECOMES TOKENS
The model does not read letters like humans. It reads these pieces, then predicts the next one.
Simple meaning
Tighten prompts, cap history, retrieve fewer better chunks, and cache embeddings and repeated prefixes.
WHY — Tokens instead of words?
LLMs use tokens (not full words) because it helps them:
question about Cost.
trade-offs, and what you would actually do on a GenAI / LLM project - not buzzwords.
Each piece maps to a number the network can learn.
Fixed pieces are what transformers expect as input.
STEPS — What happens with tokens?
Before the model can read a sentence, it goes through these steps:
- 1Tighten prompts, cap history,
retrieve fewer better chunks, and cache embeddings and repeated prefixes.
- 2Route simple intents to
a small model.
- 3Measure cost per successful
task, not only tokens per call.
- 4Context mix
Attention looks at nearby tokens together.
- 5Next token
The model scores what should come next.
- 6Decode
IDs turn back into readable text.
EXAMPLE — See it in action
Let's see how a real sentence is tokenized (tokens may vary by model):
Note: Actual tokens and IDs depend on the tokenizer (e.g., GPT, Llama, etc.).
Key takeaway
Tighten prompts, cap history, retrieve fewer better chunks, and cache embeddings and repeated prefixes. Route simple intents to a small model.