New issue
Advanced search Search tips

Issue 781254 link

Starred by 1 user
Status: Duplicate
Merged: issue 780502
Owner: ----
Closed: Nov 2017
Cc:
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.1%-180.8% regression in system_health.common_mobile at 512799:512885

Project Member Reported by mustaq@chromium.org, Nov 3 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=781254

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=72518dc24b820321a5b6e673ccbb20aae44e4abc31dc401d6bb8f23272bcadef


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

android-nexus6
android-nexus7v2
android-webview-nexus5X
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 3 2017

Mergedinto: 780502
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : total:500ms_window:renderer_eqt_max/browse_social/browse_social_tumblr_infinite_scroll
  Change       : 173.80% | 765.4365 -> 2095.73383333

Revision             Result                  N
chromium@512798      765.436 +- 104.86       6      good
chromium@512824      838.386 +- 328.821      9      good
chromium@512825      1863.5 +- 841.448       6      bad       <--
chromium@512826      1726.34 +- 930.508      6      bad
chromium@512828      1934.45 +- 368.574      6      bad
chromium@512831      1710.16 +- 2007.98      9      bad
chromium@512837      1892.66 +- 773.509      6      bad
chromium@512849      2095.73 +- 397.827      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.tumblr.infinite.scroll system_health.common_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934563997410608


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


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

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 30.95% | 2870.82433333 -> 3759.44

Revision             Result                  N
chromium@512798      2870.82 +- 383.306      6      good
chromium@512824      3025.4 +- 352.431       6      good
chromium@512825      3774.91 +- 304.947      6      bad       <--
chromium@512826      3849.46 +- 364.312      6      bad
chromium@512828      3743.22 +- 261.772      6      bad
chromium@512831      3811.01 +- 283.978      6      bad
chromium@512837      3663.96 +- 309.821      6      bad
chromium@512849      3759.44 +- 286.503      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.pinterest.infinite.scroll system_health.common_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934381489808992


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 3 2017 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_qq


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq system_health.common_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963934373966640256


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment