gecko-dev/gfx/wgpu/player
Dzmitry Malyshau abaaa872a5 Bug 1634425 - Integrate WebGPU API tracing r=jgilbert
This is the logic of tracing the WebGPU API calls at the level of wgpu-core,
serialized into a folder of choosing on the user drive. Traces are extremely portable,
they can be shared (on BugZilla) and then replayed on the developer machine,
which can have a different architecture from the users machine.

The standalone player is introduced in `gfx/wgpu/player`, similar to WebRender's Wrench.

The output dir is controlled by "dom.webgpu.traceDir" pref. No tracing happens if it's empty.

Differential Revision: https://phabricator.services.mozilla.com/D73333
2020-05-27 16:49:03 +00:00
..
src Bug 1634425 - Integrate WebGPU API tracing r=jgilbert 2020-05-27 16:49:03 +00:00
Cargo.toml Bug 1634425 - Integrate WebGPU API tracing r=jgilbert 2020-05-27 16:49:03 +00:00
README.md Bug 1634425 - Integrate WebGPU API tracing r=jgilbert 2020-05-27 16:49:03 +00:00

README.md

wgpu player

This is application that allows replaying the wgpu workloads recorded elsewhere.

Launch as:

player <trace-dir>

When built with "winit" feature, it's able to replay the workloads that operate on a swapchain. It renders each frame sequentially, then waits for the user to close the window. When built without "winit", it launches in console mode and can replay any trace that doesn't use swapchains.

Note: replaying is currently restricted to the same backend, as one used for recording a trace. It is straightforward, however, to just replace the backend in RON, since it's serialized as plain text. Valid values are: Vulkan, Metal, Dx12, and Dx11.