Open
Bug 1335546
Opened 7 years ago
Updated 1 year ago
Slim down WebGL API validation?
Categories
(Core :: Graphics: CanvasWebGL, task, P3)
Tracking
()
NEW
People
(Reporter: jujjyl, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [gfx-noted])
Attachments
(1 file)
|
348.13 KB,
image/png
|
Details |
webgl_call_validation.png
Benchmarking a WebGL 2 heavy demo, a number of the WebGL spec related validation operations come up high in AMD CodeXL profiles. See the attached image for an illustration of hottest functions in xul.dll when running the demo. Can these be optimized to be faster, or could some of them be removed, relying on the GL driver to do some of that workload? Some of the validation is useful for generating user friendly error messages, but perhaps those could be put behind a GL "developer mode" flag, since they are only interesting at development time.
|
||
Updated•7 years ago
|
|
Reporter | |
Updated•7 years ago
|
Blocks: webgl-perf-parity
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•