3 ms·
GPU memory allocation in Vulkan seems to be a huge headache. That seems to be the underlying cause of this ray tracing problem. It's exposed to the higher level
by Animats 4y ago
GPU memory allocation in Vulkan seems to be a huge headache.
That seems to be the underlying cause of this ray tracing problem. It's exposed to the higher levels, but in strange ways.
I use the Rend3->wgpu->Vulkan chain, and can't get any info about how much GPU memory is available or left. If I load too many textures into an NVidia 3070, they spill into main memory and rendering continues, slowly. If I load too many meshes, I get a fatal error from the Rend3->WGPU layer, because the allocation that failed happens long after I made the request to load a mesh and it's too late to just return an error for the request.
Can anyone explain why it's so hard to find out the memory allocation situation in Vulkan?
- yw3410 4y agoAre you using the memory budget extension? https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VK_EXT_memory_budget.html https://registry.khronos.org/vulkan/specs/1.3-extensions/man...
- Animats 4y agoNo, that's two levels below me. Rend3->WGPU is trying to abstract over OpenGL, Vulkan, Metal, and Direct-X 11/12, which creates problems in this area. Something to discuss with those devs.
- yw3410 4y agoI wonder if it has anything to do with the WebGPU standards not allowing it for browsers, or even maybe that it's not actually a meaningful question from WebGPU's point of view (iirc, they have their own allocator).