Closed
Bug 1541135
Opened 6 years ago
Closed 3 years ago
Try switching all fp32 textures to fp16 in WebRender
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: kvark, Unassigned)
Details
(Keywords: perf)
Switching to fp16 would reduce the data pushed to GPU and sampled by the shaders. It would also improve compatibility with ES2 Android devices.
The textures include GPU cache texture and the floating-point primitive header part.
Possible issues to keep in mind:
- hardware support for fp16 formats
- precision of local positions, transformation matrices, etc
Reporter | ||
Updated•6 years ago
|
Summary: Try switching all fp32 textures to fp16 → Try switching all fp32 textures to fp16 in WebRender
Comment 1•6 years ago
|
||
FWIW you can also upload f32 data to f16 textures, if that's useful as an intermediary step. If there's not a ton of data, it might be acceptable to just have the driver do the f32->f16 conversion.
Comment 2•3 years ago
|
||
We tried this on a couple of platforms, without noticeable wins. In future, we'll likely remove use of fp32 textures.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•