Resurrect the Vulkan memory visualizer, but now it's global stats and pushbuffer stats. #17011
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hrydgard
force-pushed
the
vulkan-memory-visualizer
branch
2 times, most recently
from
0ee8ebd to
9ca7975
Compare
hrydgard
force-pushed
the
vulkan-memory-visualizer
branch
from
9ca7975 to
5d5e02d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not as visually interesting as the old pre-VMA one, but useful:
Overhead should be minimal.
The point is to check and improve the push buffer sizing algorithms (or replacements for them such as ring buffers) and see the impact on memory usage. Currently the pushbuffers can go to rather extreme sizes when loading high-res texture replacement packs, and we need to get smarter, it seems.