--
[1] nVidia actually implements Vulkan on top of their OpenGL driver, but nVidia's drivers have been relatively well optimized in terms of CPU usage already. AMD is the bigger winner here.
--
[1] nVidia actually implements Vulkan on top of their OpenGL driver, but nVidia's drivers have been relatively well optimized in terms of CPU usage already. AMD is the bigger winner here.
Vulkan fixes this big time, by allowing apps to construct GPU workloads for a single GPU in parallel. Only the final submission step (which is supposed to be very low overhead if the driver design is decent) is single-threaded per GPU context. And even for that Vulkan is better: It allows you to allocate different contexts for separate engines (e.g. rendering vs. compute vs. copy engine for data up/download to/from the GPU vram).
The lower CPU overhead is just the icing on the cake, the real deal is that Vulkan fixed the threading/locking model.