I've used streamline for debugging performance recently. The workflow seems fine to me: use performance report; analyze GPU counters and use graphics analyzer in case GPU bound; analyze CPU counters and use call paths/functions in case CPU bound
The analyze part is kind of a trouble to me. There are a lot of counters so I often don't know where to start and how to detect problem from there. I watched some use cases in the document but I think I want to hear out more of your cases about how you quickly detect the performance problems and are there anything like symptom pattern?
Thanks in advance for all of your helps
Have you found the Performance Counter guide for your specific GPU? They are available here:
* https://developer.arm.com/documentation#q=Mali%20Performance%20Counters
I would like to do more documentation around the overall analysis workflow, but I'm not aware of anything we have at the moment.
Cheers, Pete
First of all, thanks for your help
I've already skimmed through it yet forgot that page. I'm sure to use it from now on
I've kind of expect the behavior similar to the advisor's one. For example, when I click on a frame or use caliper, it shows me the top 3 bottle neck and which counters I should look into for more details; or just show me which counters make my game run slow. Does streamline has something like that?
And it's nice to have more advices from you when debugging performance. I hope I can increase my speed and accuracy