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

Issue 693456 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.4% regression in smoothness.sync_scroll.key_mobile_sites_smooth at 450873:450898

Project Member Reported by alexclarke@chromium.org, Feb 17 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=693456

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguNOqvQoM


Bot(s) for this bug's original alert(s):

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 17 2017

Cc: wangxianzhu@chromium.org
Owner: wangxianzhu@chromium.org

=== Auto-CCing suspected CL author wangxianzhu@chromium.org ===

Hi wangxianzhu@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xianzhu Wang
  Commit : af710fcae8e5585e8628cd46d6f18786cc7ccb26
  Date   : Thu Feb 16 07:03:11 2017
  Subject: Avoid false-positives of paint offset change detection

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.sync_scroll.key_mobile_sites_smooth
  Metric       : frame_times/http___mobile-news.sandbox.google.com_news_pt0
  Change       : 1.71% | 16.6331395976 -> 16.9182445487

Revision             Result                    N
chromium@450872      16.6331 +- 0.132097       6      good
chromium@450879      16.5907 +- 0.225484       6      good
chromium@450882      16.6358 +- 0.0738017      6      good
chromium@450883      16.8955 +- 0.226885       6      bad       <--
chromium@450884      16.9164 +- 0.0986263      6      bad
chromium@450885      16.9244 +- 0.10277        6      bad
chromium@450898      16.9182 +- 0.104777       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mobile.news.sandbox.google.com.news.pt0 smoothness.sync_scroll.key_mobile_sites_smooth

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8987421903876900272

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5885295423127552


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: WontFix (was: Untriaged)
I think we can accept this, given that the change have much bigger performance improvement to other test cases. 
Cc: benhenry@chromium.org
Hey wangxianzhu - which other test cases do you notice an improvement? Can you point them out as I'm not able to find them now?
I associated several improvement alerts to this bug. You can browser them here: https://chromeperf.appspot.com/group_report?bug_id=693456
Labels: Performance-Responsiveness
Labels: Performance-Tradeoff

Sign in to add a comment