DirectDraw Performance Test (Compact 7)
3/12/2014
The DirectDraw Performance Test measures the performance characteristics of blitting and flipping scenarios.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following tables show the hardware requirement for the DirectDraw Performance Test.
| Requirement | Description |
|---|---|
DirectDraw-capable display hardware |
The display hardware must be accessible via a DirectDraw-compliant display driver |
The following tables show the software requirements for the DirectDraw Performance Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, required for executing tests. |
Kato.dll |
Logging engine, required for logging test data. |
Perf_DDraw.dll |
Test cases that exercise DirectDraw and output the performance statistics. |
You must include Microsoft DirectX and DirectDraw in your operating system (OS) design in order to run the DirectDraw test. The SYSGEN_DDRAW sysgen variable adds the required functionality to your OS design.
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
1 |
"Blt performance test (one pixel and full surface):" Exercises the following blit scenarios and outputs performance markers for each: * Video to video blit with one surface, full surface * Video to video blit with one surface, one pixel * Video to video blit with two surfaces, full surface * Video to video blit with two surfaces, one pixel. |
2 |
"Blt performance test (System to Video 1 pixel, full surface):" Exercises the following blit scenarios and outputs performance markers for each: * System to video blit with two surfaces, full surface * System to video blit with two surfaces, one pixel. |
3 |
"Blit performance test (system to system one pixel, full surface):" Exercises the following blit scenarios and outputs performance markers for each: * System to system blit with one surface, full surface * System to system blit with one surface, one pixel * System to system blit with two surfaces, full surface * System to system blit with two surfaces, one pixel. |
4 |
"Blit performance test (video to video 10x scaled, non-overlapping 100px):" Exercises the following blit scenarios and outputs performance markers for each: * Video to video blit with one surface, full surface * Video to video blit with one surface, one pixel * Video to video blit with two surfaces, full surface * Video to video blit with two surfaces, one pixel. |
5 |
"Blit performance test (system to video 10x scaled, non-overlapping 100px):" Exercises the following blit scenarios and outputs performance markers for each: * System to video blit with two surfaces, full surface * System to video blit with two surfaces, one pixel. |
6 |
"Blit performance test (system to system 10x scaled, non-overlapping 100px):" Exercises the following blit scenarios and outputs performance markers for each: * System to system blit with one surface, full surface * System to system blit with one surface, one pixel * System to system blit with two surfaces, full surface * System to system blit with two surfaces, one pixel. |
7 |
"Color key blit test:" Tests video-to-video color key blitting and outputs performance markers. |
8 |
"Flip performance test:" Tests backbuffer flipping with one backbuffer and outputs performance markers. |
9 |
"Lock performance test:" Tests video memory read/write performance. |
10 |
"Lock performance test:" Tests system memory read/write performance. |
Setting Up the Test
This test has no additional requirements, beyond the standard test environment setup.
Running the Test
Command line parameters for the DirectDraw Performance Test:
| Command line parameter | Description |
|---|---|
-novsync |
Disables vsync, if present (default is true) |
-YUV |
Use YUV color space, if present (default is RGB) |
-file file_name |
Specify test file name |
-platform platform_name |
Specify platform name |
-width n |
Specify surface width (default is 640) |
-height n |
Specify surface height (default is 480) |
Verifying the Test
Verify that the test is marked as passed and check the result file CePerf_DDrawResults.xml.
Troubleshooting the Test
If the tests fail or skip, make sure that you have added SYSGEN_DDRAW=1 to your image.
If you have specified custom parameters in the command line and the tests are failing, run it without any parameters and compare the results.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.