Reading a Profile Report
Turn measurements into decisions.
Reading a Profile Report is a free Mojo Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Mojo Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What a Report Shows
A profile report lists where your program spent its time, function by function, turning raw runs into clear decisions.
Total vs Self Time
Total time includes everything a function calls; self time is just its own work. Comparing the two reveals the true cost center.
Call Counts Matter
A report shows how often each function ran. A cheap call made millions of times can top the list on count alone.
Sort by Time Spent
Order the report by self time so the worst offenders rise to the top. The first row is usually where to start optimizing.
Spot the Hot Function
The function eating the largest share is your hot spot. Even a small speedup there moves the whole program forward.
Read Percentages, Not Just Seconds
A percentage of total runtime is easier to compare than raw seconds. It instantly shows which line dominates the run.
Watch for Surprises
Reports often expose a slow spot you never suspected. Let the numbers correct your intuition rather than confirming a guess.
Distinguish Compute from Memory
Some reports flag time lost waiting on data. Knowing whether the cost is compute or memory points you to the right fix.
Compare Before and After
Save a report, make a change, then profile again. Comparing the two reports proves whether your optimization really worked.
Avoid Over-Reading Noise
Tiny differences between runs are just noise. Only trust gaps large and repeatable enough to stand out across several runs.
Turn Data into a Plan
End every read with one clear action: which function to fix next. A good report becomes a focused optimization plan.
Quick Check
Think about which number to trust in a report.
Recap
You learned to read a report: compare total and self time, weigh call counts, sort by cost, ignore noise, and turn it into a plan. 📊
Frequently asked questions
Is the “Reading a Profile Report” lesson free?
Yes — the full text of “Reading a Profile Report” is free to read here on the web, and the Mojo Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Mojo Academy course, upgrade to CoddyKit PRO.
What will I learn in “Reading a Profile Report”?
Turn measurements into decisions. You practise Mojo Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Mojo Academy?
No prior experience is required. Mojo Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Reading a Profile Report” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Mojo Academy lesson?
Yes. Every Mojo Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Timing and Benchmarking Tools
- Finding the Real Bottleneck
- Optimizing What Matters
- Reading a Profile Report