New issue
Advanced search Search tips

Issue 769695 link

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



Sign in to add a comment

3.1%-8.1% regression in speedometer at 503032:503175

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

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 28 2017 

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

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


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

android-nexus5
chromium-rel-win7-gpu-nvidia
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 28 2017 


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

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

Revision             Result                  N
chromium@503070      493.748 +- 29.6664      21      good
chromium@503175      496.931 +- 33.617       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --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/8967205661930278768


For feedback, file a bug with component Speed>Bisection

Comment 4 by hablich@chromium.org, Sep 29 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment