New issue
Advanced search Search tips

Issue 773836 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 775944
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.1% regression in system_health.common_desktop at 507399:507489

Project Member Reported by nzolghadr@chromium.org, Oct 11 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 11 2017

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 11 2017


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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_tools/load_tools_stackoverflow

Revision             Result                      N
chromium@507398      0.0978134 +- 0.0450173      21      good
chromium@507489      0.100817 +- 0.0208902       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=load.tools.stackoverflow system_health.common_desktop

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Oct 27 2017

Mergedinto: 775944
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Nektarios Paisios
  Commit : 2c8739dff9cd72a0a8d4325fc6d26393df882bb0
  Date   : Mon Oct 09 17:41:57 2017
  Subject: Stops ignoring clickable elements.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : browser_accessibility_events_avg/load_accessibility_shopping/load_accessibility_shopping_amazon
  Change       : 10.96% | 3.47076258859 -> 3.85130331426

Revision             Result                   N
chromium@507377      3.47076 +- 5.58835       14      good
chromium@507394      3.03166 +- 2.82905       9       good
chromium@507399      2.86273 +- 1.38056       9       good
chromium@507400      2.67131 +- 0.401805      6       good
chromium@507401      3.62768 +- 0.913013      9       bad       <--
chromium@507403      3.60375 +- 0.805032      9       bad
chromium@507411      3.6789 +- 1.56641        14      bad
chromium@507444      3.8513 +- 2.54203        14      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=load.accessibility.shopping.amazon system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment