New issue
Advanced search Search tips

Issue 785737 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-4.4% regression in speedometer at 516201:516270

Project Member Reported by bmeurer@google.com, Nov 16 2017 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5X
chromium-rel-win7-gpu-ati
Project Member

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


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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@516215      502.889 +- 32.9991      21      good
chromium@516270      507.667 +- 33.2416      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/8962786267918761296


For feedback, file a bug with component Speed>Bisection

Comment 4 by bmeu...@chromium.org, Nov 16 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment