Guru3D.com
  • HOME
  • NEWS
    • Channels
    • Archive
  • DOWNLOADS
    • New Downloads
    • Categories
    • Archive
  • GAME REVIEWS
  • ARTICLES
    • Rig of the Month
    • Join ROTM
    • PC Buyers Guide
    • Guru3D VGA Charts
    • Editorials
    • Dated content
  • HARDWARE REVIEWS
    • Videocards
    • Processors
    • Audio
    • Motherboards
    • Memory and Flash
    • SSD Storage
    • Chassis
    • Media Players
    • Power Supply
    • Laptop and Mobile
    • Smartphone
    • Networking
    • Keyboard Mouse
    • Cooling
    • Search articles
    • Knowledgebase
    • More Categories
  • FORUMS
  • NEWSLETTER
  • CONTACT

New Reviews
GALAX GeForce RTX 4070 Ti EX White review
Cougar Terminator gaming chair review
G.Skill TridentZ5 RGB DDR5 7200 CL34 2x16 GB review
ASUS TUF Gaming B760-PLUS WIFI D4 review
Netac NV7000 2 TB NVMe SSD Review
ASUS GeForce RTX 4080 Noctua OC Edition review
MSI Clutch GM51 Wireless mouse review
ASUS ROG STRIX B760-F Gaming WIFI review
Asus ROG Harpe Ace Aim Lab Edition mouse review
SteelSeries Arctis Nova Pro Headset review

New Downloads
HWiNFO Download v7.42
Intel ARC graphics Driver Download Version: 31.0.101.4257
CrystalDiskInfo 9.0.0 Beta4 Download
AIDA64 Download Version 6.88
GeForce 531.41 WHQL driver download
AMD Radeon Software Adrenalin 23.3.2 WHQL download
GeForce 531.29 WHQL driver download
AMD Ryzen Master Utility Download 2.10.2.2367
AMD Radeon Software Adrenalin 23.3.1 WHQL download
Display Driver Uninstaller Download version 18.0.6.1


New Forum Topics
The AMD Ryzen All In One Thread /Overclocking/Memory Speeds & Timings/Tweaking/Cooling Part 2 NVIDIA GeForce 531.41 WHQL driver Download & Discussion Impending 5800x3d purchase :) What to do with an old 3800x? Help someone :) AMD Software: Adrenalin Edition 22.40.43.05 for The Last of Us™ Part 1 Release Notes Review: Cougar Terminator gaming chair RTX 4080 Owner's Thread The Last of Us Part I PC Port Receives 77% negative ratings on Steam, due to poor optimization DLSS2FSR (CyberFSR) Reporting a bug "nvlddmkm" errors event id 0 \Device\Video3




Guru3D.com » News » Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks

Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks

by Hilbert Hagedoorn on: 03/23/2017 04:39 PM | source: | 50 comment(s)
Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks

Futuremark just released 3DMark v2.3.3663 with support for Vulkan in their API overhead test, we ran some quick tests to see what is happeing.

This means you can now compare the API performance of Vulkan, DirectX 12, and DirectX 11 with one easy-to-use test. Vulkan is a new graphics API that provides high-efficiency, low-level access to modern GPUs in a wide variety of devices from PCs to smartphones. APIs like Vulkan and DirectX 12 make better use of multi-core CPUs to streamline code execution and eliminate software bottlenecks, particularly for draw calls. Games typically make thousands of draw calls per frame, but each one creates performance-limiting overhead for the CPU. Vulkan and DirectX 12 reduce that overhead, which means more objects, textures and effects can be drawn to the screen. 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 number of draw calls per second achieved by each API before the frame rate drops below 30 FPS. The Vulkan test replaces the Mantle test found in previous versions. Now I did chart up some results, see below:

 
 
The purpose of the test is to compare the relative performance of different APIs on a single system. 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. It more for you to see how much faster or slower DX12 is compared to Vulkan. You'll notice that the AMD Radeon card scores are way off. Again, this is not a graphics GPU test, but a test that shows your system API renderer performance in relation towards your setup. I have no clue about the AMD results as they are, I did run them three times and even re-installed drivers and re-seated the cards into another slot. I also have to mention that in the past we stepped away from the API test as the results back then also showed a lot of platform inconsistency.
 
Though overall Vulkan might be a notch slower compared to D3D12, it certainly is shaping up to become a very fast API. Talking about platforms, I figured why not quickly compare Ryzen 7 1700 versus Core i7 5960X (both 8-cores / 16-threads).

 

You will notice that Core i7 5960X is clocked at 4.3 GHz. The Ryzen 7 1700 is clocked at 4.1 GHz, it is the highest frequency we can obtain stable. Not bad really, the 1200 USD Intel processor is faster, especially combined with quad-channel and a 200 MHz x8 cores advantage. That 329 USD Ryzen 7 is holding up nicely.

Now I also ran the Ryzen Platform with the Fury X to be certain there isn't a bug on the X99 platform causing this behaviour:
 


 

So moving the Radeon Fury X towards a completely different system did not change the performance bracket at all. There might be a bug in the current AMD drivers, Futuremark still has some fixing to do or it just is what it is.



Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks




« Futuremark 3DMark v2.3.3663 Released - Adds Vulkan Support + Benchmarks · Quick test: Futuremark 3DMark v2.3.3663 Vulkan API Overhead Benchmarks · AMD Ryzen 5 1600 already selling »

Related Stories

Quick Test: 3DMark TimeSpy DirectX 12 Benchmarks - 07/15/2016 11:29 AM
For those that missed the news. it seems that Time Spy, the new DirectX 12 benchmark test from Futuremark is available as DLC right now on Steam, coming soon to all Windows editions of 3DMark. With i...

Quick test: DirectX 12 API Overhead Benchmark results - 03/26/2015 08:09 PM
As you guys know, DirectX 12 is going to greatly free up processor utilization, and thus your games can make more draw-calls with your processor. More efficient usage of CPUs with multiple cores is tr...

NVIDIA PhysX Quick Test - 06/20/2008 01:47 PM
As you guys likely know NVIDIA issued a new PhysX supporting driver to the press, which (driver) actually already got leaked. This driver will enable and allow a significant set of Physics functions t...


10 pages « < 5 6 7 8 > »


mtrai
Senior Member



Posts: 1183
Joined: 2013-09-21

#5411676 Posted on: 03/24/2017 02:00 AM
I am just finding this interesting that with the Vulkan support added we are also noticing the DX11 discrepancies.

Redemption80
Senior Member



Posts: 18495
Joined: 2009-01-06

#5411686 Posted on: 03/24/2017 02:26 AM
chumanga1 mentioned it has always been like this with HT enabled.

HeavyHemi
Senior Member



Posts: 6952
Joined: 2008-10-27

#5411707 Posted on: 03/24/2017 04:28 AM
As a note to others, the Vulkan API test has the same bug as does Doom using the Vulkan render in game: if you are running another nvidia model GPU, it will select that one to render vice your primary GPU.

Srsbsns
Senior Member



Posts: 190
Joined: 2015-01-28

#5411708 Posted on: 03/24/2017 04:30 AM
Why is the Fury X coming in so much behind the RX 480 when the Fury X is a much stronger card?

Robbo9999
Senior Member



Posts: 1721
Joined: 2012-10-07

#5411738 Posted on: 03/24/2017 08:17 AM
Well thanks 3DMark for breaking your bench and figuring out how to introduce a hardware fault... The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1

The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.





Futuremark has nothing to do with fixing how an API works in games.

Well, finally got it to run...who knows?


DirectX 11 single-thread
2 377 030 Draw calls per second

DirectX 11 multi-thread
2 454 589 Draw calls per second

DirectX 12
33 556 899 Draw calls per second

Vulkan
20 729 572 Draw calls per second
May as well post my results too, interesting that your DX12 results are higher than Vulkan, for me it's the other way around, yet we both have Intel/NVidia.

DX11 mult:i 4,507,018
DX12: 27,231,630
Vulkan: 29,736,051

Anyone know why our results are swapped around & so different?

10 pages « < 5 6 7 8 > »


Post New Comment
Click here to post a comment for this news story on the message forum.


Guru3D.com © 2023