Benchmarks

3DMark definition files let you set up and run benchmarks with standard or custom settings. By default, these definition files are found in C:\Program Files\UL\3DMark\.

Benchmarks

The default definitions are the same as running a test from the GUI.

Benchmarks with custom settings

Custom definition files mirror the options available on the Custom tab of the GUI. Copy the appropriate custom definition file and edit it to match your desired settings. Note that custom runs only produce sub-scores, never an overall score.

Feature tests

Stress tests

Unlimited Mode

In Unlimited mode, the benchmark runs offscreen using a fixed time step between frames. Unlimited mode renders exactly the same frames in every run on every device. You can use Unlimited mode to make chip-to-chip comparisons without vertical sync, display resolution scaling, and other operating system factors affecting the result. 

Examples

timespy.3dmdef

<?xml version="1.0" encoding="utf-8"?>
<benchmark>
  <application_info>
    <selected_workloads>
      <selected_workload name="TimeSpyDemoP"/>
      <selected_workload name="TimeSpyGt1P"/>
      <selected_workload name="TimeSpyGt2P"/>
      <selected_workload name="TimeSpyCpuP"/>
    </selected_workloads>
  </application_info>
</benchmark>

The test names are fairly self-explanatory, for example, "TimeSpyDemoP" is the demo, "TimeSpyGt1P" the Graphics test 1, and so on. Note that you will only get an overall score when all sub-tests are included.

If all you want is to specify which tests to run (for example, to skip the Demo), just make a copy of the appropriate definition file and edit the list of tests.

stresstest_firestrike_performance.3dmdef

<?xml version="1.0" encoding="utf-8"?>
<benchmark>
  <application_info>
    <selected_workloads>
      <selected_workload name="FireStrikeGt1XST"/>
    </selected_workloads>
  </application_info>
  <settings>
       <setting>
         <name>loop_count</name>
         <value>20</value>
       </setting>
    </settings>
</benchmark>

The stress test definitions function in a similar manner to other definition files but must also contain a valid loop count setting (between 2 and 5000).

Note that when specifying file paths in a custom definition file, for example for outputting frames via the Image Quality Tool feature, do not add quotation marks around the path or the test will fail.

Setting command-line options with .3dmdef files

Some command-line settings can be set within .3dmdef files, for both default and custom benchmark runs. 

If the same setting is set from both the command line and the .3dmdef file, the value differing from the default value will be used. For example, if --debug-log=off is specified on the command line, but the .3dmdef file contains the code below, then the debug log will be enabled since it is the non-default setting.

    <setting>
      <name>enable_debug_log</name>
      <value>1</value>
    </setting>

The table below lists all settings that can be set within a .3dmdef file.

enable_debug_log

0

--debug-log=off

swapchain_height

0 (auto)

swapchain_width

0 (auto)

enable_audio

1

--audio=on

enable_systeminfo_monitor

0

--systeminfomonitor=off

enable_systeminfo_collect

0

--systeminfo=off

gpu_count

0 (auto-detect)

scaling_mode

centered

--scalingmode=centered

Note that using the --scalingmode setting on the command line always overrides the value in .3dmdef file.

Using custom settings

Custom workloads have separate identifiers. For example, to run Fire Strike with a non-default resolution or other setting:

  <application_info>
    <selected_workloads>
      <selected_workload name="FireStrikeDemoC"/>
      <selected_workload name="FireStrikeGt1C"/>

Specifying the "C" version of each workload name is required for the custom settings to have an effect. If another name (for example FireStrikePhysicsP) is used, all custom settings that could potentially affect the score will be ignored.