- Joined
- Oct 9, 2007
- Messages
- 47,297 (7.53/day)
- Location
- Hyderabad, India
| System Name | RBMK-1000 |
|---|---|
| Processor | AMD Ryzen 7 5700G |
| Motherboard | ASUS ROG Strix B450-E Gaming |
| Cooling | DeepCool Gammax L240 V2 |
| Memory | 2x 8GB G.Skill Sniper X |
| Video Card(s) | Palit GeForce RTX 2080 SUPER GameRock |
| Storage | Western Digital Black NVMe 512GB |
| Display(s) | BenQ 1440p 60 Hz 27-inch |
| Case | Corsair Carbide 100R |
| Audio Device(s) | ASUS SupremeFX S1220A |
| Power Supply | Cooler Master MWE Gold 650W |
| Mouse | ASUS ROG Strix Impact |
| Keyboard | Gamdias Hermes E2 |
| Software | Windows 11 Pro |
Futuremark is 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. It's also the very first public application to use DirectX 12 full stop. This is cutting edge stuff! Developed 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.
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. 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. (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.)
DOWNLOAD: Futuremark 3DMark v1.5.884
Why is API overhead important?
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.
A draw call happens when the CPU tells the GPU to draw an object on the screen. Games typically make thousands of draw calls per frame, but each one creates performance-limiting overhead for the CPU.
As the number of draw calls rises, graphics engines become limited by API overhead. New APIs like DirectX 12 and Mantle reduce that overhead allowing more draw calls. With more draw calls, a game engine can draw more objects, textures and effects to the screen.
How does the 3DMark API Overhead feature test work?
The 3DMark API Overhead feature test measures API performance by making a steadily increasing number of draw calls. The result of the test is the maximum number of draw calls per second achieved by each API before the frame rate drops below 30 fps.
What are the system requirements?
3DMark Windows v1.5.884
March 26, 2015
This major update adds the API Overhead feature test, the world's first independent test for comparing the performance of DirectX 12, Mantle, and DirectX 11. See how many draw calls your PC can handle with each API before the frame rate drops below 30 fps.
View at TechPowerUp Main Site
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. 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. (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.)
DOWNLOAD: Futuremark 3DMark v1.5.884
Why is API overhead important?
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.
A draw call happens when the CPU tells the GPU to draw an object on the screen. Games typically make thousands of draw calls per frame, but each one creates performance-limiting overhead for the CPU.
As the number of draw calls rises, graphics engines become limited by API overhead. New APIs like DirectX 12 and Mantle reduce that overhead allowing more draw calls. With more draw calls, a game engine can draw more objects, textures and effects to the screen.
How does the 3DMark API Overhead feature test work?
The 3DMark API Overhead feature test measures API performance by making a steadily increasing number of draw calls. The result of the test is the maximum number of draw calls per second achieved by each API before the frame rate drops below 30 fps.
What are the system requirements?
- The DirectX 12 test requires a PC running an up-to-date version of Windows 10 Technical Preview (build 10041 or later), 4 GB of system memory, and DirectX feature level 11_0 compatible hardware with at least at least 1 GB of graphics memory.
- The Mantle test requires 4 GB of system memory and AMD hardware that supports the Mantle API.
- The DirectX 11 test requires DirectX feature level 11_0 compatible hardware with at least 1 GB of graphics memory and 4 GB of system memory.
3DMark Windows v1.5.884
March 26, 2015
This major update adds the API Overhead feature test, the world's first independent test for comparing the performance of DirectX 12, Mantle, and DirectX 11. See how many draw calls your PC can handle with each API before the frame rate drops below 30 fps.
- Compare DirectX 12, DirectX 11 and Mantle with the new API Overhead Feature Test, available in 3DMark Advanced Edition and 3DMark Professional Edition.
- Added Feature Test selection screen.
- Improved
- Improved formatting of larger scores to make them more readable.
- Result screen automatically shows FPS after running a single test.
- Fixed a bug that could cause the Sky Diver demo to hang at the cave entrance scene.
View at TechPowerUp Main Site
