Bug 846842 (gl-thread)

Offload OpenGL commands to a dedicated GL thread

NEW
Unassigned

Status

()

Core
Graphics
--
enhancement
5 years ago
6 months ago

People

(Reporter: jgilbert, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: webgl-perf)

(Reporter)

Description

5 years ago
We're seeing non-trivial overhead for GL calls in WebGL-heavy demos. One way to help with this is to do the actual GL calls on a different thread, synchronizing as necessary.

Most GL commands can be async, while others (bufferData, texImage2D) should often be sync.
(In reply to Jeff Gilbert [:jgilbert] from comment #0)
> We're seeing non-trivial overhead for GL calls in WebGL-heavy demos. One way
> to help with this is to do the actual GL calls on a different thread,
> synchronizing as necessary.
> 
> Most GL commands can be async, while others (bufferData, texImage2D) should
> often be sync.

FWIW, some OpenGL stacks already support this. i.e. on OS X you can opt in and on mesa there are patches to add support.
(Reporter)

Comment 2

5 years ago
Great, sounds like we should try those out as well. Doing it ourselves provides a couple other potential advantages, but more immediate solutions (for even a subset of platforms) could be quite useful.
(Reporter)

Updated

2 years ago
Blocks: 1268629
(Reporter)

Updated

2 years ago
Whiteboard: webgl-perf
(Reporter)

Updated

2 years ago
Severity: normal → enhancement
You need to log in before you can comment on or make changes to this bug.