PLO — Session 2: Performance and latency
CLO: By the end of this session, the student can set a tail-latency budget for a media path, measure which stage consumes it, and size an instance by measurement rather than by plan label.
| PLO | Role | Research answer | Lab evidence | Points | Evidence | Rubric |
|---|---|---|---|---|---|---|
| PLO1 | primary | 4 | 3 | 7 | An 800–1,200-word tail-latency budget with 5–8 sources; the latency table with its colo, the origin-versus-edge p95, the cache MISS → HIT, the memory failure and the disk-preserving resize |
Research 4/3/2/1; Lab 3/2/1/0 |
| PLO2 | secondary | 0 | 0 | 0 | Lecture context only; not scored | — |
| Total | 4 | 3 | 7 |
Total: 7 points
Four-level descriptors
Research (4/3/2/1). 4 = a clear budget with p95 targets, a stage-by-stage split, a measurement plan and a counterargument about tail amplification. 3 = a sensible budget with some measurement and one under-analysed stage. 2 = describes latency and bandwidth but does not set a budget or propose a measurement. 1 = a summary with fewer than five sources or no argument. 0 = nothing submitted or misconduct.
Lab (3/2/1/0). 3 = origin and edge are measured with the colo recorded, the cache MISS → HIT and the HTML control are explained, the memory failure and the disk-preserving resize are shown, teardown and cost respected. 2 = measurements are mostly complete but one comparison is missing or thin. 1 = partial measurements and incomplete teardown. 0 = nothing submitted, unsafe data, or no teardown.
The full course arithmetic is in production/baseline.md; this file is the weekly instance.