Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following sections describe features for use in performance testing and improvement, such as queries, counters, timing, and predication.
Tip
Before implementing custom timestamp queries, consider using PIX for Windows for GPU profiling. PIX provides timing captures, GPU occupancy visualization, and per-draw-call cost analysis without requiring any code changes. For automated regression testing, the PIX programmatic capture API allows integration into CI pipelines.
In this section
| Topic | Description |
|---|---|
| Stream-Output Counters, UAV Counters, Queries, and Predication |
Stream output and UAV counters operate in Direct3D 12 in a similar method to Direct3D 11, although now memory for the counters must be allocated by the app, the driver does not do it. Queries in Direct3D 12 are more different from those in Direct3D 11, with the addition of fences and other processes that remove the need for some query types. |
| Timing |
This section covers querying timestamps, and calibrating the GPU and CPU timestamp counters. |
| Predication |
Predication is a feature that enables the GPU rather than the CPU to determine to not draw, copy or dispatch an object. |