If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Slim down WebGL API validation?

NEW
Unassigned

Status

()

Core
Canvas: WebGL
P3
normal
8 months ago
7 months ago

People

(Reporter: Jukka Jylänki, Unassigned)

Tracking

(Blocks: 1 bug, {feature})

53 Branch
feature
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted])

Attachments

(1 attachment)

(Reporter)

Description

8 months ago
Created attachment 8832221 [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.
Keywords: feature
Priority: -- → P3
Whiteboard: [gfx-noted]
(Reporter)

Updated

7 months ago
Blocks: 1207170
You need to log in before you can comment on or make changes to this bug.