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

Issue 760570 link

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



Sign in to add a comment

127.4%-188.1% regression in loading.desktop at 497977:498054

Project Member Reported by pmeenan@chromium.org, Aug 30 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 30 2017 

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

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


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

chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 30 2017 


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/FarsNews

Revision             Result                  N
chromium@497976      512.011 +- 495.514      21      good
chromium@498039      503.71 +- 590.646       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=FarsNews loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Kicked a few more bisects.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Oct 18 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14e8b11b780000

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

Status: WontFix (was: Untriaged)
Bisect can't repro.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Oct 18 2017 


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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/FarsNews

Revision             Result                  N
chromium@497963      528.888 +- 498.0        21      good
chromium@498033      531.956 +- 638.424      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=FarsNews loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection
►

Sign in to add a comment