Skip to content
Clairos Learn

Cost, capacity, and reliability · Lesson 3 of 14 · 6 min

Compare model cost profiles

Model cost comparison should use the same workload and required quality. A cheaper request that repeatedly fails the task may not be the better operating choice.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Model cost comparison should use the same workload and required quality. A cheaper request that repeatedly fails the task may not be the better operating choice.

Interpret the evidence

Hold model B because it failed the required quality gate despite lower unit cost.

A tempting mistake

Select the lowest price regardless of whether the task succeeds.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-cost-reliability-003.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "model_a_cost": 0.002,
  "model_b_cost": 0.001,
  "a_quality_pass": true,
  "b_quality_pass": false
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .b_quality_pass /opt/ai-lab/cases/aiops-cost-reliability-003.json
false

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'hold-cheaper-failure' > /home/learner/lab/aiops-cost-reliability-003-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “hold-cheaper-failure” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Compare model cost profiles” justify?

Apply it elsewhere

A colleague concludes: “Select the lowest price regardless of whether the task succeeds.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Inspect cache effectivenessTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Estimate request costA token cost estimate multiplies each token count by its corresponding per-token rate. Convert per-million rates before summing input and output estimates.Practice
  2. 02Inspect cache effectivenessCache effectiveness depends on hit rate, eligible work and correctness. A high hit rate is harmful when responses come from stale or improperly shared entries.Practice
  3. 03Read concurrency limitsConcurrency limits bound in-flight work; they do not directly state requests per second. Throughput also depends on service time and workload size.Practice