Replies: 2 comments
-
|
A lot of debugging tools can't connect to sandboxed processes. In Google Chrome, to disable the sandbox on the GPU process you need With "Enable command line on non-rooted devices" you can pass this (and other) flags using a text file, e.g.: I don't know if this will help but it's a good first step. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks - I gave that a go, though unfortunately did not get anywhere. In Android GPU Inspector, I am able to connect to the device, though Chrome does not still show up on the list as programs to profile: 
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After getting desktop performance at a good level, I have now been shifting my renderer focus to work on mobile Android Chrome.
I find that I'm not getting as great of a performance on Android GPUs that I was hoping, and I've exhausted the major optimization items that I can think of. My renderer is massively GPU bound, while CPU usage is very low at ~10%.
So I was thinking to use the native Android profilers to do more advanced profiling:
I tried the first two programs. First, set up "Enable command line on non-rooted devices", "Unsafe WebGPU Support" and "WebGPU Developer Features" in chrome://flags, and then attempted to connect them to the device.
Android GPU Inspector installs a test program "GAPID - Vulkan Sample" onto the device. I was able to profile that program with both AGI and Arm Performance Studio.
But Chrome process does not show up as an Android program to attach to in either of these profilers.
I wonder does there currently exist a path to get any of these profilers working for WebGPU-in-Chrome? It would be great to be able to see more detailed performance information at the Vulkan low level on Android, to see if there are any inefficiencies that I could catch that way.
Beta Was this translation helpful? Give feedback.
All reactions