New issue
Advanced search Search tips

Issue 752061 link

Starred by 1 user
Status: Duplicate
Owner:
tebbi@chromium.org
Closed: Aug 2017
Cc:
tebbi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1%-3513.7% regression in v8.runtimestats.browsing_mobile at 489866:489985

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

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

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

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


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

android-nexus5
android-nexus5X
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac-retina
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 3 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Optimize:duration_avg/browse_news/browse_news_qq

Revision             Result                     N
chromium@489872      0.267048 +- 0.0623935      21      good
chromium@489896      0.259286 +- 0.0964587      21      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=browse.news.qq v8.runtimestats.browsing_mobile

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 22 2017

Mergedinto: 750299
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : Helen Li
  Commit : 73f7cac54a1108eac07d5c7c3367f979a899a0bd
  Date   : Thu Jul 27 14:57:57 2017
  Subject: [wpr-go] Switch system_health_mobile.json to use go

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Parse:duration_avg/browse_media/browse_media_imgur
  Change       : 29.94% | 1615.2215 -> 2098.8215

Revision             Result                  N
chromium@489895      1615.22 +- 105.205      6      good
chromium@489913      1669.42 +- 95.8627      6      good
chromium@489922      1643.42 +- 225.088      6      good
chromium@489923      2093.98 +- 67.8856      6      bad       <--
chromium@489924      2120.8 +- 69.3754       6      bad
chromium@489926      2103.4 +- 91.5075       6      bad
chromium@489930      2143.93 +- 78.1391      6      bad
chromium@489964      2098.82 +- 68.5923      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.media.imgur v8.runtimestats.browsing_mobile

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

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


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

Sign in to add a comment