Qt
Internal/Contributor docs for the Qt SDK. Note: These are NOT official API docs; those are found at https://doc.qt.io/
Loading...
Searching...
No Matches
profiling.qdoc
Go to the documentation of this file.
1// Copyright (C) 2026 The Qt Company Ltd.
2// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
3
4/*!
5\page qtquick-profiling.html
6\ingroup qtquick-tools
7\title Profiling QML Applications
8\brief Provides information on how to use QML's profiling tools.
9
10\section1 QML Profiler
11
12With the \l{\QC: Profiling QML Applications}{QML Profiler} you can analyze
13your QML code for performance performance issues. The profiler is part of
14both \QC and \QDS. The best way to use it is to utilize \{QC}'s or \{QDS}'s
15defaults for build and run settings.
16
17If you are building or running manually, in order to use the QML Profiler,
18you need to enable the \l{QML debugging infrastructure}.
19
20\section1 Using the command line qmlprofiler tool
21
22Qt provides the \l{qmlprofiler} command line tool to capture profiling data in a
23file. The file can later be loaded into \QC or \QDS for analysis. It
24\l{Connecting to applications}{connects} to the application using the
25debugging protocol.
26
27To run this tool, after starting the application with the
28\l{QML debugging infrastructure} enabled, enter the following command:
29
30\c {qmlprofiler -p <port> -attach <ip address>}
31
32It is advisable to use the \c{services} argument to \c{-qmljsdebugger} in order to
33limit the debug infrastructure to only the services required. These are typically
34\c{CanvasFrameRate}, \c{EngineControl}, and \c{DebugMessages}. Having other services
35enabled may influence the profiling results.
36
37*/