Shipped on Android and FirefoxOS. Usable on Linux and Mac (buggy and off by default). Work in progress on Windows.
The main goal is to improve responsiveness. this architecture has the following advantages over our on-the-main-thread approach:
- Reduce main thread contention
- Asynchronous scrolling
- Preventing tearing
- Asynchronous video
- Asynchronous CSS animation
A new thread will handle composition. This thread will receive updates from the content thread, much as the chrome process receives updates from the content process in e10s. Indeed, as much as possible, the shadow layers machinery developed for e10s will be adapted for off-main-thread compositing. The design may need to diverge in some places from the e10s approach: for example, on Android, updates from the content thread to the compositing thread need to be asynchronous. (note: With the current code ... this might not be the case with the new frontend, and even in the current code, the cases that require async PLayers could be fixed at the widget/android level too. We'll need to make a tradeoff.)
Our highest priority platform for this project has been mobile platforms, but we want to extend this to all supported platforms: Mac, Windows (D3D9 + D3D10), Linux, and software-only (BasicLayers; possibly, there is ongoing discussion as to whether this is the best use of resources to improve the experience for 'low-end' users).
- Only scrolling is asynchronous/off main thread. All other features require further work.
- Android and B2G: Released. We continue to iron out OMTC bugs as the test base expands, but we are already quite high-quality.
- OS X: bug 756601 Alpha quality. We began development of OMTC on this platform, but we haven't worked on it much since then. It pretty much works but is disabled by default.
- Linux: bug 722012 In initial implementation stages. We're still sorting out basic issues with X and GL, as we don't support OMTC with BasicLayers yet.
- BasicLayers (software only): bug 703484 In initial implementation stages. Marco Castelluccio, a volunteer contributor, is working through implementing off-main-thread BasicLayers, which also involves making our Cairo library thread-safe.
- Direct3D 10: bug 756606 Work in progress; has some fundamental problems with textures which require the layers refactoring.
- Direct3D 9: bug 756608 Work in progress; but, in theory, should be fairly straightforward (there are already shadow layers implemented, but I don't think they are used anywhere).
The WebGL streaming buffer project helped improve our WebGL compositing performances. Even though there is stil some work in progress, most of the work has landed already.
- Sharing WebGL backing textures between threads bug 728524 lets us avoid reading back.
- Double-buffering WebGL bug 716859 lets us hand off a texture to the compositor, then go back to drawing to the WebGL context.
- Not using glFinish() to synchronize between threads bug 697831 (most likely using the ARB_sync extension) will let us hand those textures off faster.
Assignee: Jeff Giblert, Cody Brocious (Daeken)
Status: Mostly done
The video pipeline can now decode and composite video frames without touching the content thread (async-video). To improve performances and audio/video synchronization, there is some work in adding synchronization logic on the compositor side.
- Asynchronous video composition (already landed) is bug 706172
Assignee: Nicolas Silva (nical)
Status: async-video done, improvements planned.
Currently CSS animations are driven by the main thread. It'd be better if the style and layout code could assign attributes to relevant layers that would then be interpolated using specified functions on the compositor thread.
- Asynchronous CSS animation is bug 706179
Assignee: David Zbarsky (dzbarsky) Status: Being worked
Plugins are already drawn asynchronously (at least on OS X), similarly to how HTML5 video works. Publishing those plugin "frames" to the compositor is directly analagous.
Status: No work done
Animated images are drawn using the main thread, but at least conceivably we could publish all the frames to the compositor and have the compositor know how to animate the images.
This could help us to animate throbbers, etc, but we don't currently have any layers support at all for animated images, so it will be more work for potentially less gain.
Assignee: Joe Drew
Status: Work in progress
Off-main-thread layers implementations
Features listed above won't work off the main thread unless we have a layers implementation that knows how to draw off the main thread.
The layers system has been heavily refactored to more easily facilitate OMTC on all platforms.
The biggest changes are to the compositing side, and to how textures/buffers/handles are passed between the drawing and compositing components. The aim is for most OMTC code to be backend-independent. Compositing is done by a Compositor class (rather than the ShadowLayerManager, which still have responsibility for managing the shadow layer tree). There are backend-specific compositor sub-classes, but the shadow layer tree and it's manager are backend-independent. Buffers/textures are handled by TextureClient/TextureHost pairs which have backend-specific subclasses and handle all inter-thread communication. The layer classes can then be agnostic about backend and IPC mechanism.
The Gecko overview wiki page contains good documentation about the current (post refactoring) layers system.
Assignee: Benoit Girard/Ali Juma
Mac OS X
Status: Beta quality
Assignee: Nicolas Silva
Status: In development, testable but buggy not optimized.
Assignee: Nick Cameron
Status: In development
Assignee: Bas Schouten
Status: Alpha quality
This layers implementation is used when we have no hardware-accelerated layers backend; for example, when we're on a system with too-old drivers.
Assignee: Marco Castelluccio
Status: In development
Development is happening on mozilla-central.