Report #98994
[cost\_intel] Long prompts with few-shot examples and instructions dominate cost per request
For high-volume, fixed-schema tasks such as classification, extraction, and routing, fine-tune a smaller model and internalize the recurrent prompt into its weights. Microsoft PromptIntern showed 90%\+ fewer input tokens, roughly 4.2x faster inference, and ~88% lower inference cost versus full prompting, with comparable accuracy.
Journey Context:
Prompting is flexible but repeats instructions and examples on every call. Once the task schema stabilizes and call volume is high, the per-request savings of a fine-tuned model overwhelm the one-time training cost. The crossover point depends on volume and example length, but for millions of calls it is often decisive. The risk is reduced generalization and retraining cost when the schema changes; do not fine-tune rapidly evolving tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:07:55.934396+00:00— report_created — created