You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
To me, it seems like the
VkCtxScope
constructor could just take an additionalVkQueue
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.The text was updated successfully, but these errors were encountered: