The Runtime Theory
medium · 3h · 9 steps

Performance Engineering: Measure Before Optimizing

Use workload shape, queueing, profiling, and query evidence to locate the dominant cost before changing code.

Curriculum (9 steps)

1

Latency measures how long one operation takes; throughput measures how many operations complete per unit time.

Start→
2

An interactive concept flow for latency, throughput, and queueing are linked, from its assumptions through the main operation and boundary checks.

Start→
3

Profiling attributes resource use to parts of a running program; benchmarking compares defined workloads under controlled conditions.

Start→
4

Follow the key state changes and boundary checks involved in profile before rewriting the slow path.

Start→
5

Use a repeatable matrix workload to compare loop order, profile cache behavior, and report what the measurement can support.

Start→
6

Database performance depends on how many rows and pages a query touches, how much data moves between operators, and whether the working set fits in memory.

Start→
7

Follow the key state changes and boundary checks involved in find the data access that dominates query cost.

Start→
8

An interactive concept flow for find the data access that dominates query cost, from its assumptions through the main operation and boundary checks.

Start→
9

Explain the model, execution steps, complexity, and limits of profile before rewriting the slow path.

Start→