New issue
Advanced search Search tips

Issue 788631 link

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



Sign in to add a comment

3.8%-5.1% regression in speedometer at 517926:518166

Project Member Reported by hablich@chromium.org, Nov 27 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 27 2017 

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

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


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

android-one
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 27 2017 


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : speedometer
  Metric       : VanillaJS-TodoMVC/VanillaJS-TodoMVC

Revision             Result                  N
chromium@517975      251.722 +- 27.2652      21      good
chromium@518088      255.041 +- 38.3005      21      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by hablich@chromium.org, Nov 27 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment