mirror of
https://github.com/wolfpld/tracy.git
synced 2024-11-22 14:44:34 +00:00
Update manual.
This commit is contained in:
parent
1f68b739af
commit
8b0da6f508
@ -16,6 +16,7 @@
|
||||
\usepackage{hyperref} % For hyperlinks in the PDF
|
||||
\usepackage{fontawesome5}
|
||||
\usepackage[os=win]{menukeys}
|
||||
\usepackage{xfrac}
|
||||
|
||||
\usepackage[hmarginratio=1:1,top=32mm,columnsep=20pt]{geometry} % Document margins
|
||||
\geometry{a4paper,textwidth=6.5in,hmarginratio=1:1,
|
||||
@ -1537,6 +1538,14 @@ You have instrumented your application and you have captured a profiling trace.
|
||||
|
||||
The workflow is identical, whether you are viewing a previously saved trace, or if you're performing a live capture, as described in section~\ref{interactiveprofiling}.
|
||||
|
||||
\subsection{Time display}
|
||||
|
||||
In most cases Tracy will display an approximation of time value, depending on how big it is. For example, a short time range will be displayed as 123~\si{\nano\second}, and some longer ones will be shortened to 123.45~\si{\micro\second}, 123.45~\si{\milli\second}, 12.34~\si{\second}, 1:23.4, 12:34:56, or even 1d12:34:56 to indicate more than a day has passed.
|
||||
|
||||
While such presentation makes time values easy to read, it is not always appropriate. For example, you may have multiple events happen at a time approximated to 1:23.4, giving you a precision of only $\sfrac{1}{10}$ of a second. There's certainly a lot that can happen in 100~\si{\milli\second}.
|
||||
|
||||
To solve this problem, an alternative time display is used in appropriate places. It combines a day--hour--minute--second value with full nanosecond resolution, resulting in values such as 1:23~456,789,012~\si{\nano\second}.
|
||||
|
||||
\subsection{Main profiler window}
|
||||
|
||||
The main profiler window is split into three sections, as seen on figure~\ref{mainwindow}: the control menu, the frame time graph and the timeline display.
|
||||
|
Loading…
Reference in New Issue
Block a user