Skip to main content

S1: GC and interval WAF

Question: Why does a logical write require extra media work?

Time: 30 minutes. Prerequisites: completed setup. See qualification and limitations before running.

Mechanism​

Garbage collection copies live pages before erasing a victim line
The FEMU Manual shows why live-page relocation adds media work beyond host writes.
  1. Overwrite invalidates an older physical page.
  2. Garbage collection relocates valid pages and erases a victim.
  3. Counters expose data, GC, mapping and padding writes.

Predict​

What happens to relocation work as the occupied fraction increases?

Write down a predicted state or counter change before executing the commands.

Run​

Host terminal, unless a command is explicitly labelled Guest. Source and export the identity fields from connection.env. These labs overwrite the explicit disposable namespace. Use a fresh VM for each independent arm.

bash labs/bin/preflight.sh labs/guest/lab-s1-waf.sh /dev/nvme0n1

Check your evidence​

  • The measured phase writes 16 GiB with CRC verification.
  • Compute deltas from the same controller and interval.
  • Check whether GC actually ran before explaining its cost.

The host runner retrieves raw receipts and preserves the guest exit status. Keep unsuccessful attempts; do not replace them with a later successful log.

Interpret​

When does a two-term WAF numerator miss modeled media work?

Explain the mechanism and the measurement boundary. A throughput number by itself is not evidence that the intended feature was exercised.

Recover​

  • Counter decrease: reject the comparison; the device may have reset.
  • No GC: inspect occupancy and working set.
  • Never divide by a zero host-write denominator.

Save the receipt before resetting the VM.

Materials and source​

Slides, scripts and worksheet. Videos are not yet recorded. The frozen public source is 1918eb9795ba. The FEMU Manual explains the implementation and supported properties.