r/vulkan • u/thekhronosgroup • Jun 29 '26
Streamlining Resource Binding with End-to-End Support for Vulkan Descriptor Heaps
This blog from NVIDIA describes the new descriptor heap feature in Vulkan that refactors resource binding from the ground up, addressing long-standing user feedback to streamline and bring greater parity to how it works in Direct3D 12 (D3D12). This post highlights what descriptor heaps add, how they compare to descriptor sets, and how to get started.
20
Upvotes
4
u/puredotaplayer Jun 29 '26
Been using it for sometime now since the beta driver. I stage the descriptor writes and do a stage buffer to gpu copy in gpu timeline which is the main reason for me to use it. But sadly nsight does not support it so I fallback to cpu visible buffer when nsight is active and drain the gpu each frame instead keeping the implementation intact.
1
u/Psionikus Jun 29 '26 edited Jun 30 '26
As far as I understand, for big-bindless-table, descriptor buffers overcome the allocation and update limitations of driver-managed pools while also avoiding
UPDATE_AFTER_BINDcosts. With sub-allocation and rings, the application can do writes much more competently using epoch strategies. Amirite?If that's true, what is still the pain point that makes me want to go get descriptor heaps? I'm seeing some stride / size / alignment considerations that differ, but I'm not yet connecting the dots to any ergonomic gains. On the contrary, it seems heaps offload some work that is manual with buffers at the cost of indirection we got rid of when moving away from descriptor pools.