Scarfski/tracy
1
0
Fork 0
mirror of https://github.com/wolfpld/tracy.git synced 2026-11-07 08:25:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Achievements text tweaks.

Browse Source
This commit is contained in:
Bartosz Taudul
2026-10-31 18:13:29 +01:00
parent 16ca4f5913
commit 76bdf0cdb7
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
profiler/src/achievements/FindZone.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Find some zones
To find a zone, open the [Find zone window](#findzone) with the * Find* button on the top bar and type in the zone name — in most cases the function name in the code.
To find a zone, open the [Find zone window](#findzone) with the * Find* button on the top bar and type in the zone name, in most cases the function name in the code.
1. If several zones share the name, a list of matches is shown. Select the one you're looking for.
2. The window shows a histogram of execution times, along with statistics such as total time, mean, and median.
profiler/src/achievements/LightFlame.md
+2 -2
View File
@@ -1,7 +1,7 @@
# Light the flame
The timeline shows what happened when: every zone drawn at its exact duration, on its own thread. The [flame graph](#flamegraph) answers the other question, where the total time went. It merges all threads and sums every run of each zone per call stack, so a box's width is total time, not a single execution.
The timeline shows what happened, with every zone drawn at its exact duration on its own thread. The [flame graph](#flamegraph) answers the other question: where the total time went. It merges all threads and sums every run of each zone per call stack, so a box's width is total time, not a single execution.
Open it with the * Flame* button on the top bar. In *Instrumentation* mode the tree is built from your zones; hovering a box shows its execution and self time, clicking jumps to the zone statistics. In *Sampling* mode the tree is built from call stack samples, and clicking a box opens the source code.
Open it with the * Flame* button on the top bar. In *Instrumentation* mode the tree is built from your zones. Hovering a box shows its execution and self time, clicking jumps to the zone statistics. In *Sampling* mode the tree is built from call stack samples, and clicking a box opens the source code.
Open the flame graph and see where the time goes. Try it out!
profiler/src/achievements/LoadTrace.md
+1 -1
View File
@@ -2,4 +2,4 @@
You can open a previously saved trace file (or one received from a friend) with the * Open saved trace* button on the welcome screen. After the trace is loaded, the [Analyzing captured data](#analyzingdata) chapter describes what you can do with it.
Trace files are version-specific: a trace from a newer Tracy version will fail to open, but traces from older versions load fine — only very old traces are rejected.
Trace files are version-specific: a trace from a newer Tracy version will fail to open, but traces from older versions load fine. Only very old traces are rejected.
profiler/src/achievements/Manual.md
+1 -1
View File
@@ -2,7 +2,7 @@
Tracy ships with a built-in user manual that describes all of its features. You can open it by clicking the * Manual* button in the top toolbar of the profiler window or on the welcome screen.
It's an alternative to external documentation — always available offline, and it covers everything from basic instrumentation to advanced sampling and memory profiling.
It's an alternative to external documentation that is always available offline and covers everything from basic instrumentation to advanced sampling and memory profiling.
> [!TIP]
> **Tip**
profiler/src/achievements/ReadAssembly.md
+1 -1
View File
@@ -2,7 +2,7 @@
Tracy copies more than source files into the trace. It also copies your program's machine code: the exact instructions your functions were compiled into. The source view can therefore show you what each line you wrote was turned into. Choose *Source* only, machine *Assembly* only, or *Both* side by side with the *Mode* selector at the top of the window.
To see which instructions matter, enable [call stack sampling](#sampling). Tracy then interrupts the program repeatedly and records where in the code it was interrupted. Every instruction gets a percentage showing how often the interruptions caught it running. The instructions caught running most often are the ones eating your time; you can spot them by their percentages. The brightest are the hottest.
To see which instructions matter, enable [call stack sampling](#sampling). Tracy then interrupts the program repeatedly and records where in the code it was interrupted. Every instruction gets a percentage showing how often the interruptions caught it running. The instructions caught running most often are the ones eating your time. You can spot them by their percentages. The brightest are the hottest.
The compiler inlines calls, fuses loops, and reorders instructions, so a harmless-looking source line can hide the instruction that eats up the time.