Theme Catppuccin
Make yourself at homeCatppuccin

A softer light for long learning sessions.

Appearance

Loading your preference…

Dark palette

Choose a dark palette to try it.

Light uses Latte. Your choices stay in this browser.

Measure one bottleneck

SKETCHBOOK / 07 The Living Gallery · 2-week chapter

Page 1 of 4: Choose the question before the timer

Measurement / workload

Choose the question before the timer

Pick a gallery operation that matters: time to prepare one selected asset, total batch throughput, peak accepted payload, or cancellation completion latency. Those are different metrics. A faster checksum batch is not automatically a more responsive renderer.

Record machine, compiler, standard library, build mode, input, worker count, warmup policy, repetitions, and what the measurement includes. Keep a correctness checksum outside the timing decision so optimization does not remove the work or change its meaning unnoticed.

The companion reports peak active work as an invariant observation, not a benchmark. Its tiny workloads may be dominated by thread startup and coordination. Use the observation to verify a bound, and use an appropriately sized repeatable workload before making timing claims.

TRY IT IN YOUR STUDIO

Write one measurement sentence with a metric, unit, workload, and excluded costs. Reject a second sentence that makes a broader claim than the experiment supports.

From the page to your own work

Your studio assignment.

Produce one defensible Living Gallery performance investigation.

A finish line you can see

A measurement protocol, repeated results, a correctness check, and an explained tradeoff.

  1. Keep workload/build mode fixed for comparisons.
  2. Separate thread startup, batch work, and shutdown when relevant.
  3. State sanitizer coverage and untested targets.
  4. Report a result even if the proposed optimization does not help.
Keep the evidence in your weekly notebook ↗
Explain it like an engineer

Try answering aloud before opening the review notes. Use your own implementation as evidence.

What evidence would convince you that a worker-count change improved the gallery?
  • A relevant user-facing metric on a fixed workload.
  • Repeated measurements with environment and uncertainty.
  • Unchanged correctness, memory bounds, and cancellation contracts.

These prompts support practice; they are not an automatic assessment of your work.

A small creative variation ↗

Compare one and two workers on a chosen CPU batch, then explain why the result may not generalize.

Optional. Save it for later if this chapter already feels full.

Coming back after a break? ↩

Run the correctness checks once, write the metric sentence, and make one baseline measurement.

Books & principles behind this study +

Original Parallax explanations and assignments, with these works for further reading.

YOUR MARGIN NOTES

Leave yourself a good question.

What changed your mind? What would you try next?

Notes are private to this browser and saved as you write.

A CHECKPOINT, NOT A SCORE

Can you explain the idea and try the exercise yourself?

Completion records your own assessment. It does not compile or test your C++.
Companion source 14 files