NVIDIA 396.18 Linux Benchmarks, Testing Their New Vulkan SPIR-V Compiler

Written by Michael Larabel in Display Drivers on 11 April 2018 at 10:00 AM EDT. Page 2 of 6. 6 Comments.
NVIDIA Vulkan Driver SPIR-V Compiler

Dota 2 at 4K with Vulkan saw about the same frame-rate, though using the old compiler on the 396.18 release was causing greater variance. Though with the new compiler, the run-time on the first run (prior to using any cached shaders) dropped from 30 seconds to 25 seconds though on subsequent runs the run-time was similar at about 19 seconds.

NVIDIA Vulkan Driver SPIR-V Compiler
NVIDIA Vulkan Driver SPIR-V Compiler
NVIDIA Vulkan Driver SPIR-V Compiler
NVIDIA Vulkan Driver SPIR-V Compiler

With Mad Max on Vulkan, the performance was roughly in line with the old compiler. Like with Dota 2, the first run of the game prior to any shader caching was a few seconds quicker when making use of their new NVVM-based shader compiler stack..

NVIDIA Vulkan Driver SPIR-V Compiler

The CPU usage was roughly the same during this long-running benchmark.

NVIDIA Vulkan Driver SPIR-V Compiler

While the GPU memory usage was slightly higher than on the older 390.48 driver branch.

NVIDIA Vulkan Driver SPIR-V Compiler

And the GPU is kept busy pretty much constantly with this benchmark...

NVIDIA Vulkan Driver SPIR-V Compiler

On the 396.18 driver with the new shader compiler, the memory usage is about 600MB less than with the old compiler... But that actually appears to be a regression with the old compiler in moving to 396 as back on the 390.48 driver with the old compiler its system RAM usage was similar to 396.18 on the new compiler.


Related Articles