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)

enhancement
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sotaro, Assigned: sotaro)

Details

Attachments

(1 file)

It seems better to investigate for using IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used. It might get better performance.
Assignee: nobody → sotaro.ikeda.g
Summary: Use IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used → Use IDCompositionSurface instead of IDXGISwapChain when DirectComposition is used in RenderCompositorANGLE
Current RenderCompositorANGLE uses just IDXGISwapChain, since it could be used for both with/without DirectComposition.
Attached patch wipSplinter Review
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.
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.

Attachment

General

Created:
Updated:
Size: