{"id":107760,"date":"2023-04-06T12:48:22","date_gmt":"2023-04-06T10:48:22","guid":{"rendered":"https:\/\/prohoster.info\/?p=107760"},"modified":"2023-04-06T17:07:09","modified_gmt":"2023-04-06T15:07:09","slug":"v-chrome-budet-vklyuchena-podderzhka-webgpu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-chrome-budet-vklyuchena-podderzhka-webgpu","title":{"rendered":"Chrome will include support for WebGPU","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has announced the default inclusion of support for the graphics API WebGPU and the WebGPU Shading Language (WGSL) in Chrome version 113, scheduled for release on May 2. WebGPU provides a programming interface similar to Vulkan, Metal, and Direct3D 12 for performing operations on the GPU side, such as rendering and computations, and also allows the use of a shading language to write programs that run on the GPU. The implementation of WebGPU will initially be included only in builds for ChromeOS, macOS, and Windows. Support for WebGPU on Linux and Android will be enabled later. <\/p>\n
In addition to Chrome, experimental support for WebGPU has been tested in Firefox since April 2020 and in Safari since November 2021. To enable WebGPU in Firefox, the flags dom.webgpu.enabled and gfx.webgpu.force-enabled should be set in about:config. There are currently no announcements regarding plans to enable WebGPU by default in Firefox and Safari. Implementations of WebGPU for Firefox and Chrome are available in the form of separate libraries \u2014 Dawn (C++) and wgpu (Rust), which can be used to integrate WebGPU support into applications. Work is also underway to add WebGPU support to popular JavaScript libraries that originally use WebGL. For instance, full WebGPU support has already been announced in Babylon.js, with partial support in Three.js, PlayCanvas, and TensorFlow.js. <\/p>\n
Conceptually, WebGPU differs from WebGL in a way similar to how the Vulkan graphics API differs from OpenGL, yet WebGPU is not based on a specific graphics API; rather, it serves as a universal layer that uses the same low-level primitives found in Vulkan, Metal, and Direct3D. WebGPU provides JavaScript applications with tools for low-level control over the organization, processing, and dispatch of commands to the GPU, management of related resources, memory, buffers, texture objects, and compiled graphics shaders. This approach allows for higher performance in graphics applications by reducing overhead and improving the efficiency of GPU handling. <\/p>\n
WebGPU enables the creation of complex 3D projects for the web, performing as well as standalone applications that directly utilize Vulkan, Metal, or Direct3D, but without being tied to specific platforms. WebGPU also offers additional capabilities for porting native graphics applications to a format that can run on web technologies, thanks to compilation to WebAssembly. In addition to 3D graphics, WebGPU also encompasses functionalities related to offloading computations to the GPU and executing shaders. <\/p>\n
Key features of WebGPU: <\/p>\n
\n
Separate management of resources, setup operations, and command submission to the GPU (in WebGL, a single object was responsible for everything at once). Three separate contexts are provided: GPUDevice for creating resources like textures and buffers; GPUCommandEncoder for encoding individual commands, including rendering and compute stages; and GPUCommandBuffer for queuing for execution in the GPU. The result can be rendered in an area associated with one or more canvas elements or processed without output (for example, when executing compute tasks). This separation of stages simplifies the distribution of resource creation and setup operations into different handlers that can run in different threads. <\/li>\n
A different approach to state processing. WebGPU offers two objects \u2014 GPURenderPipeline and GPUComputePipeline, which allow developers to combine various pre-defined states, enabling the browser to save resources by eliminating additional tasks such as shader recompilation. Supported states include shaders, vertex buffer and attribute layouts, attached group layouts, blending, depth and stencil, as well as output formats after rendering. <\/li>\n
The binding model is largely reminiscent of the grouping resources found in Vulkan. To group resources in WebGPU, a GPUBindGroup object is provided, which can be linked with other similar objects during command recording for use in shaders. Creating such groups allows the driver to perform necessary preparatory actions in advance and enables the browser to switch resource bindings between rendering calls much faster. The layout of resource bindings can be defined in advance using a GPUBindGroupLayout object. <\/li>\n<\/ul>\n