Quantcast
Channel: GameDev.net
Viewing all articles
Browse latest Browse all 17560

How to understand GPU profiler data and use it to trace down suspicious abnormally slow GPU task?

$
0
0

Hey Guys,

 

If I got it correctly, the reason we use/implement GPU profiler is to identify any suspicious render passes/GPU tasks in our pipeline which is abnormally slow, so we could optimize the renderer more efficiently. However, sometimes I feel that it's very hard for me to identify those suspicious slow GPU jobs from GPU profiler. For example, my GPU profiler told me that it takes 1.5ms for a compute shader to copy a 1080p R8G8B8A8 image from CPU writable memory to a same format Texture2D on default heap every frame. Does that sound normal given that I am using GTX680m? 

 

I feel like most experienced graphics programmer knows roughly how long should it take for GPU to do certain tasks. I just wondering how they know it B-)

 

Thanks 


Viewing all articles
Browse latest Browse all 17560


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>