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

Issue 759702 link

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



Sign in to add a comment

41.5% regression in loading.desktop at 495833:495836

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

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

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

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


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

chromium-rel-win7-gpu-intel
Project Member

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


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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/IndiaTimes

Revision             Result                  N
chromium@495832      1044.4 +- 48.9061       21      good
chromium@495836      1056.89 +- 186.767      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=IndiaTimes loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Kicked off a few more bisects
Project Member

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


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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/IndiaTimes

Revision             Result                  N
chromium@495832      1046.22 +- 30.1544      21      good
chromium@495837      1055.56 +- 200.641      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=IndiaTimes loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection
Project Member

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


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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/IndiaTimes

Revision             Result                  N
chromium@495832      1430.88 +- 221.637      21      good
chromium@495838      1434.27 +- 122.091      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 --story-filter=IndiaTimes loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 9 by benhenry@chromium.org, Dec 12 2017

Status: WontFix (was: Untriaged)
Bisect unable to find culprit. This exists in stable. Ignoring.
►

Sign in to add a comment