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

Group GPU scopes by Vulkan queues instead of CPU thread #768

Open
spnda opened this issue Apr 11, 2024 · 0 comments
Open

Group GPU scopes by Vulkan queues instead of CPU thread #768

spnda opened this issue Apr 11, 2024 · 0 comments

Comments

@spnda
Copy link
Contributor

spnda commented Apr 11, 2024

With the current profiler, when I submit to two Vulkan GPU queues from 16 threads this will show 16 GPU timelines in the profiler for work to be done. However, I only have two Vulkan queues, and would like to see on which of these queues these operations are being executed. The GPU obviously doesn't care on which CPU thread the command buffer was generated on.
image

To me, it seems like the VkCtxScope constructor could just take an additional VkQueue handle and instead of writing the id of the current thread, we could write the queue handle. However, I'm not sure how Tracy internally handles the grouping of timelines so I don't know where to begin to make changes to support this. I'd also like to hear what other people think and if, perhaps, this functionality already exists but I just don't know about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant