We Rely On Your Support: This site is primarily supported by advertisements. Ads are what have allowed this site to be maintained for the past 14 years. We do our best to ensure only clean, relevant ads are shown, when any nasty ads are detected, we work to remove them ASAP. If you would like to view the site without ads while still supporting our work, please consider our ad-free Phoronix Premium. You can also consider a tip via PayPal.

This last week marked two years since the debut of Vulkan 1.0, you can see our our original launch article. My overworked memory missed realizing it by a few days, but it's been a pretty miraculous two years for this high-performance graphics and compute API.

In the two years that Vulkan 1.0 has been around we have seen drivers for all major platforms, not one but two open-source AMD Vulkan Linux drivers (AMDVLK and RADV), the rapid rate of ascent for the RADV and Vulkan drivers have shown how much lighter the driver implementations are than OpenGL drivers, these open-source drivers have kept up-to-date with minor specification revisions, OpenGL SPIR-V/Vulkan interoperability was introduced last year, and more game developers continue making use of Vulkan.

Also, we have seen Feral Interactive focus now on bringing their new games to Linux using Vulkan (in fact, Vulkan exclusives now) and the open-source community around Vulkan has been thriving. In fact, on GitHub is now around 1,800 projects referencing Vulkan while just 94 mention D3D12 or 38 as "Direct3D 12." On the Windows side there have been a few prominent Vulkan titles like DOOM and Wolfenstein. But sadly not as many Vulkan games as I would have hoped for now two years in, especially for cross-platform games.

Making it challenging as well is that many of the current games utilizing Vulkan aren't seeing significant performance benefits compared to their OpenGL code-paths since the engines/renderers aren't yet fully designed for making use of a low-level graphics API. We have been seeing more work in this direction and the Vulkan vs. Linux OpenGL performance improving as well as the increasing maturity of the Vulkan drivers.

What do you think of Vulkan now two years since the public release? What do you want to see added to the API? What do you think they will introduce in their next major update? Has the Vulkan tooling to date been satisfactory? What about macOS support? More convergence between OpenCL and Vulkan for compute? Will 2018 finally be "the year of Vulkan gaming"? Share your thoughts with us this weekend in the forums.

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

The mission at Phoronix since 2004 has centered around enriching the Linux hardware experience. In addition to supporting our site through advertisements, you can help by subscribing to Phoronix Premium. You can also use our NewEgg.com shopping links when making online purchases or contribute to Phoronix through a PayPal tip.