Skip to content
Clairos Learn

Models, artifacts, and runtimes · Lesson 9 of 16 · 5 min

Compare quantization profiles

Quantization changes representation and memory use, and it can affect task quality. Measure both resource behavior and held-out quality for the intended workload.

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

Quantization changes representation and memory use, and it can affect task quality. Measure both resource behavior and held-out quality for the intended workload.

Interpret the evidence

Hold this q4 candidate despite its lower memory use because it failed the quality gate.

A tempting mistake

Lower memory use automatically means a better release.

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-models-runtimes-009.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "q8_memory_gib": 8,
  "q4_memory_gib": 4.5,
  "q4_quality_pass": false
}

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

$ jq .q4_quality_pass /opt/ai-lab/cases/aiops-models-runtimes-009.json
false

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

$ printf '%s\n' 'hold-q4' > /home/learner/lab/aiops-models-runtimes-009-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-q4” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Compare quantization profiles” justify?

Apply it elsewhere

A colleague concludes: “Lower memory use automatically means a better release.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Read memory requirementsTry 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. 01Inspect tokenizer metadataToken IDs depend on the tokenizer paired with the model. A tokenizer mismatch can change segmentation and special tokens even when the input text is identical.Practice
  2. 02Read memory requirementsWeight size is not the total serving memory requirement. Leave space for the KV cache, runtime buffers and concurrent work before declaring an artifact a fit.Practice
  3. 03Inspect accelerator availabilityAccelerator availability has several layers: device visibility, driver/runtime support and free memory. A visible GPU does not prove that the model runtime can use it.Practice