<story><title>Chrome ships WebGPU</title><url>https://developer.chrome.com/blog/webgpu-release/</url></story><parent_chain><item><author>FL33TW00D</author><text>This is very exciting! (I had suspected it would slip to 114)&lt;p&gt;WebGPU implementations are still pretty immature, but certainly enough to get started with. I&amp;#x27;ve been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL.&lt;p&gt;I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fleetwood___&amp;#x2F;status&amp;#x2F;1638469392794091520&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fleetwood___&amp;#x2F;status&amp;#x2F;1638469392794091520&lt;/a&gt;)&lt;p&gt;That said, matmuls are still pretty handicapped in the browser (especially considering the bounds checking enforced in the browser). From my benchmarking I&amp;#x27;ve struggled to hit 50% of theoretical FLOPS, which is cut down to 30% when the bounds checking comes in. (Benchmarks here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;FL33TW00D&amp;#x2F;wgpu-mm&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;FL33TW00D&amp;#x2F;wgpu-mm&lt;/a&gt;)&lt;p&gt;I look forward to accessing shader cores as they mentioned in the post.</text></item></parent_chain><comment><author>antimora</author><text>Oh great!&lt;p&gt;I am one of the contributors for Burn (Rust Deep Learning Framework). We have a plan adding a WebGPU backend (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;burn-rs&amp;#x2F;burn&amp;#x2F;issues&amp;#x2F;243&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;burn-rs&amp;#x2F;burn&amp;#x2F;issues&amp;#x2F;243&lt;/a&gt;).&lt;p&gt;Here is more about the framework Burn: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;burn-rs.github.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;burn-rs.github.io&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Chrome ships WebGPU</title><url>https://developer.chrome.com/blog/webgpu-release/</url></story><parent_chain><item><author>FL33TW00D</author><text>This is very exciting! (I had suspected it would slip to 114)&lt;p&gt;WebGPU implementations are still pretty immature, but certainly enough to get started with. I&amp;#x27;ve been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL.&lt;p&gt;I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fleetwood___&amp;#x2F;status&amp;#x2F;1638469392794091520&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;fleetwood___&amp;#x2F;status&amp;#x2F;1638469392794091520&lt;/a&gt;)&lt;p&gt;That said, matmuls are still pretty handicapped in the browser (especially considering the bounds checking enforced in the browser). From my benchmarking I&amp;#x27;ve struggled to hit 50% of theoretical FLOPS, which is cut down to 30% when the bounds checking comes in. (Benchmarks here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;FL33TW00D&amp;#x2F;wgpu-mm&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;FL33TW00D&amp;#x2F;wgpu-mm&lt;/a&gt;)&lt;p&gt;I look forward to accessing shader cores as they mentioned in the post.</text></item></parent_chain><comment><author>misterdata</author><text>Looking forward to your WebGPU ML runtime! Also, why not contribute back to WONNX? (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webonnx&amp;#x2F;wonnx&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;webonnx&amp;#x2F;wonnx&lt;/a&gt;)</text></comment>