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

Issue 735908 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

129.2% regression in loading.desktop at 480904:481036

Project Member Reported by kraynov@chromium.org, Jun 22 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=735908

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjtzEngsM


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

chromium-rel-win7-x64-dual
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jun 22 2017


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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@480903      321.458 +- 694.094      21      good
chromium@481036      189.588 +- 573.067      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=IMDB loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976085178213870720

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6384877206765568


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jun 22 2017


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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@480903      216.733 +- 668.556      21      good
chromium@481036      263.432 +- 716.563      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=IMDB loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976085184965500112

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6696139929157632


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 22 2017


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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@480903      228.83 +- 673.468       21      good
chromium@481036      247.603 +- 690.105      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=IMDB loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976075719515602416

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6696139929157632


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jun 22 2017


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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@480903      243.789 +- 692.959      21      good
chromium@481036      246.725 +- 695.045      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=IMDB loading.desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8976075721102076928

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6384877206765568


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: WontFix (was: Untriaged)
This page/device seem to alternate between noisy/not noisy, not much we can do :(

Sign in to add a comment