New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 762207 link

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



Sign in to add a comment

31.8%-38.7% regression in loading.desktop at 496400:496578

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

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

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

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


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

chromium-rel-mac11
win-high-dpi
Project Member

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


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Yandex

Revision             Result                  N
chromium@496399      99.7344 +- 93.587       21      good
chromium@496527      97.2521 +- 89.7633      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 --story-filter=Yandex loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by sullivan@chromium.org, Oct 18 2017

Status: WontFix (was: Untriaged)
Too noisy to bisect.
►

Sign in to add a comment