New issue
Advanced search Search tips

Issue 790972 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
jgruber@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.3% regression in v8.browsing_mobile at 520437:520470

Project Member Reported by jgruber@chromium.org, Dec 1 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 1 2017 

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

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


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

android-nexus5X
Project Member

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


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_news/browse_news_reddit

Revision             Result                  N
chromium@520436      1332.93 +- 64.9193      21      good
chromium@520470      1337.36 +- 55.1677      21      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.news.reddit v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Comment 5 by jgruber@chromium.org, Dec 7 2017

Status: WontFix (was: Untriaged)
From the graphs it looks like this is back to baseline. Kicked off one last bisect but closing for now.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8_max/browse_chrome/browse_chrome_newtab

Revision             Result                  N
chromium@520204      181.518 +- 40.9945      21      good
chromium@520470      183.924 +- 32.8019      21      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.chrome.newtab v8.browsing_mobile

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

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


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

Sign in to add a comment