New issue
Advanced search Search tips

Issue 773213 link

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



Sign in to add a comment

3.3% regression in speedometer at 507333:507355

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 10 2017 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 10 2017 


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : speedometer
  Metric       : EmberJS-TodoMVC/EmberJS-TodoMVC

Revision             Result                  N
chromium@507332      565.365 +- 36.4504      21      good
chromium@507355      565.695 +- 34.385       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/8966135546559983616


For feedback, file a bug with component Speed>Bisection

Comment 4 by bmeu...@chromium.org, Oct 10 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment