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

Issue 761732 link

Starred by 1 user
Status: Duplicate
Merged: issue 760567
Owner: ----
Closed: Sep 2017
Cc:
█ petermarshall@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

182.2% regression in v8.runtimestats.browsing_mobile at 498179:498451

Project Member Reported by petermarshall@chromium.org, Sep 4 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 4 2017 

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

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


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

android-webview-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 4 2017 


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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-phantom-handle-callback_max/browse_shopping/browse_shopping_lazada

Revision             Result                    N
chromium@498178      0.429095 +- 0.596097      21      good
chromium@498451      0.454333 +- 0.495165      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.shopping.lazada 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/8969399647824047152


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Sep 4 2017

Mergedinto: 760567
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Dave Tapuska
  Commit : f238a1a8f2f73d226bdb38394a6e085a59cf0e41
  Date   : Mon Aug 28 21:24:39 2017
  Subject: Move Input Injection from Chrome IPC to mojo.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-phantom-handle-callback_max/browse_shopping/browse_shopping_lazada
  Change       : 149.31% | 0.1815 -> 0.4525

Revision             Result                     N
chromium@497684      0.1815 +- 0.0568111        6      good
chromium@497878      0.182667 +- 0.0406366      6      good
chromium@497879      0.182667 +- 0.0466833      6      good
chromium@497880      0.455667 +- 0.105391       6      bad       <--
chromium@497882      0.536667 +- 0.476188       6      bad
chromium@497885      0.406833 +- 0.0591171      6      bad
chromium@497891      0.467667 +- 0.458804       6      bad
chromium@497903      0.432167 +- 0.0916342      6      bad
chromium@497927      0.455833 +- 0.401799       6      bad
chromium@497975      0.4585 +- 0.0520529        6      bad
chromium@498071      0.431167 +- 0.166297       6      bad
chromium@498457      0.5325 +- 0.445874         6      bad
chromium@499230      0.4525 +- 0.0880085        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=browse.shopping.lazada 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/8969377259745692240


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

Sign in to add a comment