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

Issue 758870 link

Starred by 1 user
Status: Duplicate
Merged: issue 758701
Owner: ----
Closed: Aug 2017
Cc:
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

850.3% regression in loading.desktop at 496589:496651

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

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

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

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


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

chromium-rel-mac11-air
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 25 2017 


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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/TicketMaster

Revision             Result                  N
chromium@496619      546.727 +- 194.534      21      good
chromium@496636      549.837 +- 211.366      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=TicketMaster loading.desktop

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

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


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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 25 2017

Mergedinto: 758701
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Pavel Feldman
  Commit : 9ce7836fdec98fde42fc61347c4161077dbea0fc
  Date   : Wed Aug 23 07:07:21 2017
  Subject: DevTools: introduce lifecycle events reported over the page domain.

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/TicketMaster
  Change       : 19.73% | 450.7065 -> 539.630999998

Revision             Result                  N
chromium@496588      450.707 +- 16.6499      6      good
chromium@496604      457.109 +- 30.3507      6      good
chromium@496606      446.828 +- 49.4126      6      good
chromium@496607      571.199 +- 110.913      6      bad       <--
chromium@496608      572.044 +- 160.963      6      bad
chromium@496612      584.095 +- 78.7065      6      bad
chromium@496620      591.727 +- 132.37       6      bad
chromium@496651      539.631 +- 109.2        6      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=TicketMaster loading.desktop

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

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


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

Sign in to add a comment