Intermediate·Concept·2 min read

What do Big-O and profiling tell me?

Practice this question

Definition:

Big-O describes how an algorithm's work or memory grows as the input grows. Profiling measures where a particular application spends time or retains memory during a real workload. They complement each other: growth rate explains future scaling, while profiling locates the current bottleneck.

Key points:

  • Big-O shows how work or memory grows as input grows.

  • Profiling shows where this application actually spends time or memory.

  • Use both: a good algorithm can still be slow because of I/O or excessive queries.

  • An O(n) loop with one database call per item may be far slower than an in-memory loop with the same Big-O.

Interview point:

  • Discuss both algorithmic work and expensive operations such as network calls; a complexity label alone is not a performance diagnosis.
Adapted from 08_PERFORMANCE_SECURITY.md · “What do Big-O and profiling tell me?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.