glretrace application.trace
-Pass the `-sb` option to use a single buffered visual. Pass `--help` to
+Pass the `--sb` option to use a single buffered visual. Pass `--help` to
`glretrace` for more options.
EGL traces must be replayed with `eglretrace` instead of `glretrace`.
You can perform gpu and cpu profiling with the command line options:
- * `-pgpu` record gpu times for frames and draw calls.
+ * `--pgpu` record gpu times for frames and draw calls.
- * `-pcpu` record cpu times for frames and draw calls.
+ * `--pcpu` record cpu times for frames and draw calls.
- * `-ppd` record pixels drawn for each draw call.
+ * `--ppd` record pixels drawn for each draw call.
The results from this can then be read by hand or analysed with a script.
For example, to record all profiling data and utilise the per shader script:
- ./glretrace -pgpu -pcpu -ppd foo.trace | ./scripts/profileshader.py
+ ./glretrace --pgpu --pcpu --ppd foo.trace | ./scripts/profileshader.py
Advanced usage for OpenGL implementors
arguments << QLatin1String("-"); // emit to stdout
} else if (isProfiling()) {
if (m_profileGpu) {
- arguments << QLatin1String("-pgpu");
+ arguments << QLatin1String("--pgpu");
}
if (m_profileCpu) {
- arguments << QLatin1String("-pcpu");
+ arguments << QLatin1String("--pcpu");
}
if (m_profilePixels) {
- arguments << QLatin1String("-ppd");
+ arguments << QLatin1String("--ppd");
}
} else {
if (m_doubleBuffered) {
- arguments << QLatin1String("-db");
+ arguments << QLatin1String("--db");
} else {
- arguments << QLatin1String("-sb");
+ arguments << QLatin1String("--sb");
}
if (m_benchmarking) {