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

Issue 779814 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

7.8%-231.8% regression in smoothness.gpu_rasterization.top_25_smooth at 511313:511702

Project Member Reported by briander...@chromium.org, Oct 30 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5X
android-nexus6
android-one
chromium-rel-mac12
chromium-rel-win10
Project Member

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


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.top_25_smooth
  Metric       : input_event_latency_discrepancy/http___www.ebay.com


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.ebay.com smoothness.gpu_rasterization.top_25_smooth

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

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


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

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 31 2017

Mergedinto: 779475
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Alex Moshchuk
  Commit : 9cf0ac139cc65890b9e036f704040c8da332d6e3
  Date   : Wed Oct 25 21:26:19 2017
  Subject: Add field trial testing config for sign-in process isolation.

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_media/load_media_9gag
  Change       : 11.13% | 47768863.3333 -> 53086260.0

Revision             Result                  N
chromium@511557      47768863 +- 852760      6      good
chromium@511591      47759509 +- 280912      6      good
chromium@511593      47664027 +- 345350      6      good
chromium@511594      53169173 +- 493033      6      bad       <--
chromium@511596      53148907 +- 508831      6      bad
chromium@511600      53046289 +- 291325      6      bad
chromium@511608      53208423 +- 166080      6      bad
chromium@511625      53201734 +- 536092      6      bad
chromium@511693      53086260 +- 599658      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.media.9gag system_health.memory_desktop

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

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


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

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


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

Suspected Commit
  Author : Alex Moshchuk
  Commit : 9cf0ac139cc65890b9e036f704040c8da332d6e3
  Date   : Wed Oct 25 21:26:19 2017
  Subject: Add field trial testing config for sign-in process isolation.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_tools/load_tools_docs
  Change       : 16.15% | 19377841.6667 -> 22507323.5

Revision             Result                   N
chromium@511581      19377842 +- 167542       6      good
chromium@511589      19219912 +- 202513       6      good
chromium@511593      19282137 +- 547292       6      good
chromium@511594      22543053 +- 309305       6      bad       <--
chromium@511595      22493191 +- 156380       6      bad
chromium@511597      22230453 +- 1224735      6      bad
chromium@511612      22494290 +- 272201       6      bad
chromium@511642      22475267 +- 667865       6      bad
chromium@511702      22507324 +- 821591       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=load.tools.docs system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment