New issue
Advanced search Search tips

Issue 851906 link

Starred by 1 user
Status: Started
Owner:
hajimehoshi@chromium.org
Cc:
altimin@chromium.org
haraken@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Break down CompositorTaskRunner usage

Project Member Reported by hajimehoshi@chromium.org, Jun 12 2018 
First I'll try to add location to CompositorTaskRunner usages, run the layout tests and see task execution time, like what we did for TTRH::Get() before (https://chromium-review.googlesource.com/c/chromium/src/+/795534). Does this make sense as a start?

Of course I'd need to add a new UMA for a detailed metadata of compositor tasks to know the situation in the real world.

Comment 1 by hajimehoshi@chromium.org, Jun 25 2018

Status: Started (was: Assigned)
I measured task duration on compositor task queues on the main thread on all the layout tests:

https://docs.google.com/spreadsheets/d/1nSbPwkXlDBizUKooErUq0S2OUtx3j_jsrbpai4xftdA/edit#gid=0

The heaviest task is RenderWidgetCompositor::SynchronouslyComposite, which calls BeginMainFrame. I guess that the tendency would be same in the real world, and most task duration would come from this.

So I was wondering if it would really make sense to add annotations for each task . Would there be a better unit for annotation to break down?

Comment 2 by hajimehoshi@chromium.org, Jun 25 2018 

CL to take a measurement for task duration on compositor task queue: https://chromium-review.googlesource.com/c/chromium/src/+/1100857
►

Sign in to add a comment