# Performance symptoms — Debugging & Profiling

Source: https://www.geekswithgeeks.com/en/debugging-profiling/debugging-profiling-16

> Apply Performance symptoms with a clear goal and verifiable outcome.

## Understand Performance symptoms

For **Performance symptoms**, begin with the problem it solves. Identify the input, the constraint, and the observable result before selecting a tool or workflow. This makes your choice explainable and easier to review.

## See the working path

Use this path to practise **Performance symptoms**: understand the context, make one focused change, verify the result, then record the lesson.

![A four-stage practice workflow for Performance symptoms.](assets/figures/debugging-profiling/section-4-map.svg) — Figure 4.1 — Understand, act, verify and improve.

## A useful comparison

**Performance symptoms** is like a checklist before a journey: it cannot travel for you, but it prevents a small missed detail from becoming a costly surprise.

Check the reasoning behind the action.

**Quiz:** What is the strongest first step when using Performance symptoms?

- [x] Define the problem, constraint and evidence for success.
- [ ] Copy the largest example without reading it.
- [ ] Skip verification to save time.

*Answer:* Define the problem, constraint and evidence for success.. Clear constraints and a verifiable result make a workflow reliable.