New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 706860 link

Starred by 7 users

Issue metadata

Status: Available
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Sign in to add a comment

Create automated tests for measuring UI performance of ChromeOS

Project Member Reported by sky@chromium.org, Mar 30 2017

Issue description

We need a suite of automated tests that measures the performance of various UI operations in ChromeOS. For example, maximizing windows, interactive resizing and dragging windows...
 
Blockedon: 704285 704287
Components: UI>Shell
Labels: Proj-Mustash-Testing
Status: Available (was: Untriaged)
Blockedon: 704681
Blockedon: 177031
For those following along 177031 was proposed as a way to provide an API to UI to "flatten" a subtree for animation. Its basically SetForceRenderSurface and then have the display compositor cache render surfaces so that they're cheaper than not using a render surface (without invalidations).

Comment 5 by wutao@chromium.org, Apr 5 2017

Cc: wutao@chromium.org

Comment 6 by sadrul@chromium.org, May 12 2017

Blockedon: 721640
Cc: mfomitchev@chromium.org
Cc: fsam...@chromium.org
Adding myself to follow this bug.

Comment 9 by sadrul@chromium.org, May 12 2017

Blockedon: 721920

Comment 10 by sky@chromium.org, May 14 2017

Mikhail, any chance you would take this one over?
Owner: mfomitchev@chromium.org
I started looking at this a couple of weeks back to understand what would need to happen. I think we are in a good place. There has been some recent work to add a 'Browser' devtools API that allows changing window states etc [1]. Although these are currently only used by chromedriver [2], I think we will be able to use this from catapult too.


[1] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/inspector/browser_protocol.json?sq=package:chromium&dr&l=4666
[2] https://codereview.chromium.org/2826393002

For reference, CL implementing the 'Browser' devtools API: https://codereview.chromium.org/2813553005
Blockedon: 704670

Comment 15 by sky@chromium.org, Jun 8 2017

Blocking: 731255
Blocking: 732568
Owner: sadrul@chromium.org
Status: Started (was: Available)
I have started working on this.
Blockedon: 758060
Blockedon: 758061
Components: Speed>Benchmarks
Blocking: 759163
Owner: chiniforooshan@chromium.org
Project Member

Comment 23 by bugdroid1@chromium.org, Nov 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/1087227dc4f1b667ae1297562e95020f08c5baca

commit 1087227dc4f1b667ae1297562e95020f08c5baca
Author: Ehsan Chiniforooshan <chiniforooshan@chromium.org>
Date: Thu Nov 16 20:31:34 2017

telemetry: add window manager actions for CrOS

Same as
https://chromium-review.googlesource.com/c/chromium/src/+/660918,
but adding the new methods to the devtools client backend.

Manually tested on a chromebook and verified that we can enter/exit
overview mode using the action runner.

Bug: chromium:706860

Change-Id: I50bbf0848d2fc9b90cdc1d73277a56cdd52f6fb1
Reviewed-on: https://chromium-review.googlesource.com/758918
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ehsan Chiniforooshan <chiniforooshan@chromium.org>

[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/backends/chrome/cros_browser_backend.py
[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/actions/action_runner_unittest.py
[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/backends/browser_backend.py
[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/actions/action_runner.py
[add] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/backends/chrome_inspector/window_manager_backend.py
[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/browser/browser.py
[modify] https://crrev.com/1087227dc4f1b667ae1297562e95020f08c5baca/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py

Cc: -mfomitchev@chromium.org
Blockedon: 788442
Blockedon: 788454
Blockedon: 795928

Comment 28 by sky@chromium.org, Jan 3 2018

Blocking: -731255
Removing as a blocker for 731255 and instead we'll track the time it takes for events to be processed (798775) as well as time to initial present (792214).
Project Member

Comment 29 by bugdroid1@chromium.org, Mar 2 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/5a6deddca2a2dac34ed7c075c802ebd1ba6730de

commit 5a6deddca2a2dac34ed7c075c802ebd1ba6730de
Author: wutao <wutao@chromium.org>
Date: Fri Mar 02 21:25:09 2018

Add benchmark: cros_ui_smoothness

The patch adds one benchmark: cros_ui_smoothness.
1. Add it to ON_DUT_WHITE_LIST.
2. Add it to PERF_DAILY_RUN_TESTS.
3. Add it to ChromeOSPerf perf dashboard.

Bug: 706860
Test: can run the test by tools/perf/run_benchmark cros_ui_smoothness.
Change-Id: I97f60ae4f3189a9cd8d835f3b59ec3fa67496372
Reviewed-on: https://chromium-review.googlesource.com/943937
Commit-Ready: Tao Wu <wutao@chromium.org>
Tested-by: Tao Wu <wutao@chromium.org>
Reviewed-by: Chung-yih Wang <cywang@chromium.org>

[add] https://crrev.com/5a6deddca2a2dac34ed7c075c802ebd1ba6730de/server/site_tests/telemetry_Benchmarks/control.cros_ui_smoothness
[modify] https://crrev.com/5a6deddca2a2dac34ed7c075c802ebd1ba6730de/server/cros/telemetry_runner.py
[modify] https://crrev.com/5a6deddca2a2dac34ed7c075c802ebd1ba6730de/tko/perf_upload/perf_dashboard_config.json
[modify] https://crrev.com/5a6deddca2a2dac34ed7c075c802ebd1ba6730de/server/site_tests/telemetry_Benchmarks/generate_controlfiles.py

Owner: wutao@chromium.org
Components: Internals>Services>Ash
Labels: -Proj-Mustash-Mash
Owner: ----
Status: Available (was: Started)
sky@, you mentioned this in an email thread recently. Not sure what is the latest plan for this.
I will remove myself as the owner for now.
Owner: osh...@chromium.org
Oshima is going to take this on.

Sign in to add a comment