FS26
Ctrl K
Phase 31 · Lesson 01

Performance Budgets and Measurement

≈ 2 min core reading · 197 source/companion words
Learning contract

What you should be able to do after this

  • Explain Performance Budgets and Measurement without relying on framework buzzwords.
  • Connect the lesson to the phase outcome: Measure TaskFlow and improve bottlenecks systematically across browser, API, database, cache, and network without sacrificing correctness.
  • Reproduce the relevant behavior and verify it with evidence.
  • Diagnose at least one representative failure instead of guessing.
Figure 31.1 — TaskFlow boundary map
measure baseline
locate bottleneck
form hypothesis
change one thing
remeasure
add regression guard
This lesson belongs to Phase 31. Keep the full request/data path visible even when today's code changes only one box.
Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

Performance Budgets and Measurement

A performance budget turns “fast enough” into a falsifiable statement. TaskFlow separates browser experience, API latency, database behavior, and capacity. The exact numbers below are starting engineering targets for this course, not universal guarantees.

Boundary TaskFlow starting budget

Core Web Vitals p75 LCP <= 2.5 s, INP <= 200 ms, CLS <= 0.1

Code
GET /tasks                                                      p95 API <= 300 ms under normal target load
Code
PATCH /tasks/:id                                                p95 API <= 400 ms under normal target load

Error rate < 1% unexpected 5xx during benchmark

DB query hot path Investigate repeated queries above ~100 ms and any obvious N+1 pattern

Bundle No unexplained large client-bundle regression after dependency changes

Core Web Vitals measure user-visible browser experience and are evaluated at the 75th percentile. They do not replace backend metrics. A fast API can still produce poor LCP because the browser downloaded too much JavaScript, and a tiny JavaScript bundle cannot compensate for a two-second database query.

Field browser route/renderi repository/Pri infrastructure API latency PostgreSQL metrics ng sma saturation → → → → →

Figure 2. Separate performance layers

Production caution: Never benchmark development mode. Use production builds, representative data, warm-up, fixed scenarios, and the same environment before comparing two changes.

Executable lesson studio · performance

Now turn the explanation into engineering skill.

Performance Budgets and Measurement matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.

By the end, you should be able to

  • Explain Performance Budgets and Measurement in terms of concrete inputs, ownership, outputs, and evidence.
  • Implement or reproduce the smallest TaskFlow slice that demonstrates this performance concept.
  • Diagnose one representative performance failure using observable evidence instead of trial-and-error.
Figure 31.1B — Mental model
baseline
measurement
bottleneck
targeted change
re-measurement
Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.
Code-along sequence

One coherent change at a time

  1. 01

    Restate the goal of “Performance Budgets and Measurement” as one observable behavior. Write the success signal before touching code.

  2. 02

    Trace the boundary map: baseline → measurement → bottleneck → targeted change → re-measurement. Mark the one boundary this lesson changes.

  3. 03

    Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.

  4. 04

    Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.

  5. 05

    Connect the slice to TaskFlow’s phase artifact: Before/after performance report with measured bottleneck, change, and regression guard.. Verify behavior from the outside as a user or API client would.

  6. 06

    Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.

  7. 07

    Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

txtBaseline before optimization
GET /tasks p95: 1.8 s
  API application: 90 ms
  database: 1.61 s
  serialization/network: 100 ms
Next action: inspect query plan before changing frontend code.

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

  1. Run the narrowest relevant command or request and require a clean exit/status.
  2. Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
  3. Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.
Break it on purpose

Build debugging memory

  1. Optimizing from intuition only
  2. Change one assumption in the performance example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.
SymptomInvestigation path
Expected result does not appear

Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.

A shortcut appears to fix it

Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “Performance Budgets and Measurement” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

  1. What problem does Performance Budgets and Measurement solve in TaskFlow, and what would be observably wrong without it?
  2. Which part of the performance boundary owns the decision, and which neighboring layer must not own it?
  3. What evidence proves the happy path instead of merely suggesting it worked?
  4. Name one realistic failure or abuse case and the first place you would inspect.
  5. If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?
Lesson studio

Turn the reading into skill

01

Do it

Choose a user-visible flow and collect a baseline instead of optimizing globally.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.
02

Break it safely

Optimizing from intuition only

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.
03

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.
Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

Next.js Rendering Bundles and Core Web Vitals →