The Timelines Window in PVRTune Complete

Each timeline represents a history of events that have been emitted by the driver and subsequently captured by PVRTune over the course of a profiling session.

The settings in the PVRPerfServer Details window affect which timelines will be created in PVRTune. Enabling more data streams will increase the number of timelines available.

Having all the timelines displayed in the graph may become overwhelming, so the Timelines window shows or hides timelines via selecting the coloured check box shown on the left. By default, the Timelines window is placed bottom right.


The window splits the available timelines into several subsections.

HW Core (Hardware Core)

These timelines track timing events emitted by GPU hardware blocks. These include:

  • Compute;

  • 2D renderer;

  • 3D renderer;

  • Tile accelerator.

HW Queue (Hardware Queue)

These timelines track timing events emitted by various hardware queues. There is one per hardware core. Each queue holds pending work submitted by the driver to the GPU for execution. These timelines require synchronisation objects to be enabled, as the queues are built from the data retrieved from synchronisation objects.

Host (User Mode)

These timelines track timing events emitted by the host client driver, which are generated by API calls from OpenGL ES, EGL, and services (UM). These include glBindFramebuffer, glDraw*, eglSwapBuffers, TA kick, and texture upload events.

Host (kernel Mode)

These timelines track timing events emitted by the host kernel driver (services). As an example, this could be enqueue events such as services scheduling work for the GPU.

Sync Objects

These timelines track synchronisation objects (one per object) and the events emitted by the driver for each object. For example - object creation, destruction, update, check fail, and check pass.