[HN Gopher] GPU profiling for WebGPU workloads on Windows with C...
       ___________________________________________________________________
        
       GPU profiling for WebGPU workloads on Windows with Chrome
        
       Author : ibobev
       Score  : 59 points
       Date   : 2024-07-02 13:51 UTC (2 days ago)
        
 (HTM) web link (frguthmann.github.io)
 (TXT) w3m dump (frguthmann.github.io)
        
       | pjmlp wrote:
       | It is a sad state of affairs that after so much Web 3D push for
       | the last 15 years, Khronos advocacy of how great it is and we
       | should all be rushing out to use them, browser vendors keep
       | ignoring the need of proper developer tooling for 3D
       | applications.
       | 
       | The best we have is either SpectorJS (showing its age, WebGL
       | only), trying to differentiate between app calls and browser
       | calls in a native GPU debugger, or create an alternative,
       | completly unrelated native version, to sanely use a GPU debugger.
        
         | _factor wrote:
         | I think the bigger issue is security. GPU access is too
         | interlinked to kernel drivers. I've seen WebGPU and even WebGL
         | crash otherwise stable systems.
        
           | pjmlp wrote:
           | Yeah, however having a debugging tool, that developers have
           | to explicitly open in developer tools, for debugging shaders
           | and drivers that are always used by the browser anyway,
           | doesn't change that.
        
             | stanleykm wrote:
             | Agreed. Chrome already has flags to reduce the security
             | posture for developers. It is not outrageous to expect
             | you'd need to use those for profiling gpu shaders. This is
             | a huge gap in the browser gpu ecosystem, especially since
             | wgsl is missing features (like unrolling hints) that can
             | result in dramatically different performance vs hlsl or
             | whatever.
        
       | ossobuco wrote:
       | I've been using the webgpu inspector extension[0] and so far it's
       | proving very useful.
       | 
       | There are some occasional bugs but the author is very responsive
       | on github and quick to fix issues.
       | 
       | Couldn't get anything useful out of PIX on the other hand.
       | 
       | - [0]: https://github.com/brendan-duncan/webgpu_inspector
        
         | Twinklebear wrote:
         | I've been able to profile using PIX following this guide:
         | https://toji.dev/webgpu-profiling/pix . The WebGPU inspector
         | extension is fantastic as well
        
       | ingen0s wrote:
       | dll go brrrr
        
       ___________________________________________________________________
       (page generated 2024-07-04 23:01 UTC)