Closed
Bug 1511322
Opened 6 years ago
Closed 6 years ago
Use IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used in RenderCompositorANGLE
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sotaro, Assigned: sotaro)
Details
Attachments
(1 file)
11.37 KB,
patch
|
Details | Diff | Splinter Review |
It seems better to investigate for using IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used. It might get better performance.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Updated•6 years ago
|
Summary: Use IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used → Use IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used in RenderCompositorANGLE
Assignee | ||
Comment 1•6 years ago
|
||
Current RenderCompositorANGLE uses just IDXGISwapChain, since it could be used for both with/without DirectComposition.
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
With attachment 9029533 [details] [diff] [review], I tested IDCompositionSurface usage. It had 2 problem.
- [1] Content was slide down a bit.
To address the problem, needed to call mVisual->SetOffsetY() to adjust offset.
- [2] performance of http://arodic.github.io/p/jellyfish/ was worse than swap chain with triple buffering.
It was better than swap chain with double buffering.
attachment 9029533 [details] [diff] [review] request to call mCompositionDevice->Commit() for every rendering.
The Commit() does actual task for very call during IDCompositionSurface usage. It seeed to add more tasks.
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•