Procyon® from UL Solutions Launch MacOS Benchmarks for Multi-Platform Score Comparison New Office Productivity Battery Life Scenario Released Today From Procyon® Lenovo Focuses on Optimizing PC Hardware Testing with Procyon® Benchmarks How does the 3DMark API Overhead feature test work? With more draw calls, a game engine can draw more objects, textures and effects to the screen. New APIs like DirectX 12 and Mantle reduce that overhead allowing more draw calls. Games typically make thousands of draw calls per frame, but each one creates performance-limiting overhead for the CPU. There has been much talk this year of new graphics APIs that let developers code 'close to the metal.' And though it's natural to think of the GPU, the benefits of APIs with lower overhead are actually achieved by making better use of multi-core CPUs to streamline code execution and eliminate software bottlenecks, particularly for draw calls.Ī draw call happens when the CPU tells the GPU to draw an object on the screen. (We are working on a DirectX 12 benchmark with game-like workloads, which we expect to release soon after the public launch of Windows 10.) Why is API overhead important? The API Overhead feature test is not a general-purpose GPU benchmark, and it should not be used to compare graphics cards from different vendors. The purpose of the test is to compare the relative performance of different APIs on a single system, rather than the absolute performance of different systems. This is cutting edge stuff!ĭeveloped with input from AMD, Intel, Microsoft, NVIDIA, and the other members of our Benchmark Development Program, the 3DMark API Overhead feature test lets you compare the performance of DirectX 12, DirectX 11, and Mantle.

It's also the very first public application to use DirectX 12 full stop. We're excited to introduce our new 3DMark API Overhead feature test - the world's first independent test for measuring differences in DirectX 12, DirectX 11 and Mantle API performance.

Directx 12 feature level 11 download