Closed
Bug 846842
(gl-thread)
Opened 12 years ago
Closed 2 years ago
Offload OpenGL commands to a dedicated GL thread
Categories
(Core :: Graphics: CanvasWebGL, enhancement)
Core
Graphics: CanvasWebGL
Tracking
()
RESOLVED
DUPLICATE
of bug 1607940
People
(Reporter: jgilbert, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: webgl-perf)
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.
Comment 1•12 years ago
|
||
(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•12 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•9 years ago
|
Whiteboard: webgl-perf
Reporter | ||
Updated•9 years ago
|
Severity: normal → enhancement
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Component: Graphics → Graphics: CanvasWebGL
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•