Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor internal gpu memory naming system and use JSON dump feature of VMA #510

Open
IAmNotHanni opened this issue Oct 24, 2022 · 0 comments
Labels
cat:refactor refactor/clean up/simplifications/etc. cat:vma Vulkan Memory Allocator (VMA)

Comments

@IAmNotHanni
Copy link
Member

IAmNotHanni commented Oct 24, 2022

Is your feature request related to a problem?

We are currently not using VMA's gpu memory dump and visualization feature.

Description

Vulkan Memory Allocator has a feature where you can assign internal debug names to resources (memory allocations) and then you can dump the gpu memory as JSON using vmaBuildStatsString. This can then be used to make an image as visualization of gpu memory using VMA's GpuMemDumpVis python script.

Don't mix this VMA naming system up with resource names in Vulkan validation layers.

Alternatives

None, as we should visualize our memory usage.

Affected Code

All of the code.

Operating System

All operating systems.

Additional Context

none

@IAmNotHanni IAmNotHanni added the org:triage labels have to be specified or checked label Oct 24, 2022
@IAmNotHanni IAmNotHanni added cat:refactor refactor/clean up/simplifications/etc. cat:vma Vulkan Memory Allocator (VMA) and removed org:triage labels have to be specified or checked labels May 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat:refactor refactor/clean up/simplifications/etc. cat:vma Vulkan Memory Allocator (VMA)
Projects
None yet
Development

No branches or pull requests

1 participant