New issue
Advanced search Search tips

Issue 782183 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.3% regression in speedometer2 at 511659:511759

Project Member Reported by jarin@google.com, Nov 7 2017

Issue description

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

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


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

chromium-rel-win7-x64-dual

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : speedometer2
  Metric       : React-Redux-TodoMVC/Speedometer2
  Change       : 1.41% | 661.126857143 -> 670.425944444

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/f4051b64f4e700bc168ff667d112d5c87fa6d37b..c9c4f2aa812daf4d0df6dd09ac15896c3f9eb50d


Revision             Result                  N
chromium@511658      661.127 +- 20.473       14       good
chromium@511684      655.153 +- 14.103       14       good
chromium@511685      ---                     ---      build failure
chromium@511686      ---                     ---      build failure
chromium@511687      660.274 +- 22.5144      14       bad
chromium@511688      662.094 +- 19.0423      14       bad
chromium@511691      664.168 +- 11.1485      6        bad
chromium@511697      662.095 +- 25.7979      14       bad
chromium@511709      667.191 +- 16.9929      14       bad
chromium@511759      670.426 +- 21.0188      9        bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by jarin@chromium.org, May 15 2018

Status: WontFix (was: Assigned)
Ref also regressed.

Sign in to add a comment