Examples: Add Performance Comparison for WebGL and WebGPU Renderers #29077
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related comments: #29066 (comment) #29066 (comment)
Description
This PR introduces two new examples to compare the performance of WebGL and WebGPU renderers using a non-optimized GLTF scene. The scene consists of approximately 800 meshes and 140,000 vertices.
The goal of these examples is to provide a direct comparison of rendering performance between WebGL and WebGPU. This will help identify areas for optimization and guide further development of the WebGPURenderer.
WebGL:
https://raw.githack.com/renaudrohlinger/three.js/utsubo/feat/performance/examples/webgl_performance.html
WebGPU:
https://raw.githack.com/renaudrohlinger/three.js/utsubo/feat/performance/examples/webgpu_performance.html
Performance Observations
On a MacBook Pro M1 Max:
WebGLRenderer:
WebGPURenderer (currently forced on the WebGL Backend to highlight the difference):
/cc @mrdoob @sunag @Mugen87
This contribution is funded by Utsubo