~/talk

Vulkan Memory Management

Talkat 2018 Vulkan Montreal Dev Day · on Monday, 2018-04-30
links:none on file
slides:none on file

Vulkan pushes memory decisions to the app, so use 256 MB blocks for suballocation (drivers often cap allocations around 4,000), because individual allocations are slow and expensive. Use the transfer queue for async texture streaming and background defragmentation, but avoid GPU-to-GPU copies on that queue. Prefer optimal tiled images, avoid setting every usage bit, and keep about 20–33% free of heaps. Aliasing render targets can save up to 300 MB. The open‑source Vulkan Memory Allocator handles type selection, suballocations and dumps JSON for analysis.

AI-written summary · about

  1. 0:00Intro
  2. 0:58The challenge
  3. 1:43Advantages
  4. 2:25Memory Heaps and types
  5. 2:44Memory types: Intel
  6. 7:18Memory types: AMD APU
  7. 8:50Memory blocks
  8. 9:37Suballocation
  9. 10:35Over-commitment
  10. 13:03Transfer
  11. 16:14Resource Creation
  12. 17:53Vulkan Memory Allocator
  13. 20:13Conclusions
  14. 21:05References
  15. 21:28Thank you
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.