Disable all, Null Hardware and Disable Draw Calls
Use the
Disable all
option to disable all override modes. Use this option to reset the rendering state of the game or graphics application back to the default state.The
Null Hardware
override emulates an infinitely fast GPU by not sending any primitives to the GPU. This override is only available on systems using Intel® HD Graphics.NOTE
To enable the
Null Hardware
override, enable the Null Hardware Override Support
toggle button in the Graphics Monitor Options
screen.You can apply the
Null Hardware
override mode only to the most recent application opened for analysis. To apply this mode to an application opened previously, restart this application from the Graphics Monitor.For example, if you start the
CityRacer
application while the
gpasample
application is running, you can apply the Null Hardware
override mode only to
CityRacer
. If you close
CityRacer
, you still need to restart the
gpasample
application to use this mode.The
Disable Draw Calls
override emulates an infinitely fast driver and GPU by not sending any primitives to the driver and, therefore, to the GPU as well.NOTE
On Intel® GPUs prior to Intel® HD Graphics 3000/2000, the
Null Hardware
override implementation requires that all GPU work is blocked causing the System Analyzer HUD to not update while Null Hardware
is in effect. The display appears to "freeze" while Null Hardware
is active. On more recent GPUs, this is no longer a requirement and the System Analyzer HUD continues to update while Null Hardware
is active and you must manually toggle the override off.Run these overrides iteratively, using
Disable all
between experiments. Compare frame rate results between experiments and analyze your results based on the following table:
Performance
|
Bottleneck
|
|---|---|
Disable Draw Calls - no change
Null Hardware - no changes
|
CPU bound in the application:
use the Graphics Trace Analyzer or Intel® VTune™ Amplifier to analyze game/CPU code.
|
Disable Draw Calls - improves frame rate
Null Hardware - no changes
|
CPU bound in the driver:
use the Graphics Trace Analyzer or Intel® VTune™ Amplifier to analyze game/CPU code.
|
Null Hardware - improves frame rate
|
GPU bound:
use the Graphics Frame Analyzer to analyze the issue.
|
Use the set of
Disable all
, Null Hardware
and Disable Draw Calls
to determine if the game is CPU bound in the application, CPU bound in the driver, or GPU bound. If your application is GPU-bound, you can capture a frame with a low frame rate for a detailed analysis with the Graphics Frame Analyzer. If your application is CPU-bound, you can use the Graphics Trace Analyzer to show how the various CPU tasks within your application are being executed.