-
Notifications
You must be signed in to change notification settings - Fork 396
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
Performance issue with debugPrintfEXT using Vulkan 1.1 #7562
Comments
I have zero explanation, but thanks for doing some debugging to narrow down this to being a strange Vulkan 1.1 issue I will try and reproduce and figure out what is going on |
Oddly, I can no longer reproduce this. I had multiple SDKs installed, removed all of them and only installed the most recent one. So most probably this was a problem with my setup. Sorry for the noise. |
ok, if you see it again PLEASE report it |
Reopening this. I have submitted a PR for a shader debugprintf sample at KhronosGroup/Vulkan-Samples#945 (review) and one of the reviewers seems to have the exact same problem. I couldn't reproduce it on my machine after cleaning up SDK installs. |
In case you need a repo, we have merged the shader debugprintf sample at https://github.com/KhronosGroup/Vulkan-Samples I can now reproduce this most of the time, and others have reported that problem too. It may be the sample's fault after all, though I can't seem to see why. |
Yep I saw and plan to use that! I have as of 2 days ago, started to really get working on Debug PrintF again, it had not had any real attention towards it and so hopefully very soon (pending I'm off next week) get fixed soon Thanks for keeping this issue alive |
I can also confirm the following results for the same shader_debugprintf sample on macOS Ventura (modified to enable the portability enumeration extension and flag), using Vulkan SDK 1.3.283.0:
|
Environment:
Describe the Issue
When using
debugPrintfEXT
along withVkValidationFeaturesEXT
to fetch the debug output with a debug messenger callback, performance is so severely impacted, that the application is no longer interactive.The setup:
Application:
Vertex shader:
After some debugging with a minimal sample, I noticed that this only happens with Vulkan 1.1 (set in
VkApplicationInfo
). Using any other api version, performance is fine.Summary:
I can only imagine that the combination of
debugPrintfEXT
,VkValidationFeaturesEXT
andVK_API_VERSION_1_1
triggers an odd constellation in the layers that somehow causes a severe slowdown.Expected behavior
Using
debugPrintfEXT
withVkValidationFeaturesEXT
shows the same performance no matter what API version.Valid Usage ID
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: