New issue
Advanced search Search tips

Issue 791472 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

5%-24.2% regression in speedometer at 520437:520470

Project Member Reported by hablich@chromium.org, Dec 4 2017

Issue description

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

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


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

android-nexus5X

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : speedometer
  Metric       : FlightJS-TodoMVC/FlightJS-TodoMVC

Revision             Result                  N
chromium@520436      1009.36 +- 493.765      21      good
chromium@520470      1047.0 +- 580.342       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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Untriaged)

Sign in to add a comment