forked from qt-creator/qt-creator
Doc: Update Performance Analyzer docs
- Update Timeline screenshot with new numbers Task-number: QTCREATORBUG-30604 Change-Id: I35a4455de391a7bdaa1381dc09959ffb120431b3 Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Binary file not shown.
Before Width: | Height: | Size: 19 KiB |
Binary file not shown.
After Width: | Height: | Size: 13 KiB |
@@ -257,7 +257,7 @@
|
||||
The \uicontrol Timeline view displays a graphical representation of CPU
|
||||
usage per thread and a condensed view of all recorded events.
|
||||
|
||||
\image qtcreator-performance-analyzer-timeline.png {Performance Analyzer}
|
||||
\image qtcreator-performance-analyzer-timeline.webp {Performance Analyzer Timeline view}
|
||||
|
||||
Each category in the timeline describes a thread in the application. Move
|
||||
the cursor on an event (5) on a row to see how long it takes and which
|
||||
@@ -452,12 +452,16 @@
|
||||
\section1 Loading and Saving Trace Files
|
||||
|
||||
You can save and load trace data in a format specific to the
|
||||
Performance Analyzer with the respective entries in \uicontrol Analyze >
|
||||
\uicontrol {Performance Analyzer Options}. This format is self-contained, and
|
||||
Performance Analyzer (.ptq). This format is self-contained, and
|
||||
therefore loading it does not require you to specify the recording
|
||||
environment. You can transfer such trace files to a different computer
|
||||
without any toolchain or debug symbols and analyze them there.
|
||||
|
||||
To load trace data, go to \uicontrol Analyze >
|
||||
\uicontrol {Performance Analyzer Options} > \uicontrol {Load Trace File}.
|
||||
|
||||
To save trace data, select \uicontrol {Save Trace File}.
|
||||
|
||||
\section1 Troubleshooting
|
||||
|
||||
Performance Analyzer might fail to record data for the following reasons:
|
||||
|
Reference in New Issue
Block a user