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

Issue 666400 link

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

Blocked on:
issue 669608


Sign in to add a comment

5.4%-11.2% regression in memory.top_10_mobile_stress at 432265:432397

Project Member Reported by mustaq@chromium.org, Nov 17 2016 
See the link to graphs below.

Comment 1 by mustaq@chromium.org, Nov 17 2016 

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

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


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

android-nexus5X
android-nexus6
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 22 2016 


===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432384  1.61786  1.1875   25  good
chromium@432418  1.72885  1.53439  25  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 666400

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2281
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995271720210878128


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5788603165179904

| 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 Tests>AutoBisect.  Thank you!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 22 2016 


===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@432387  2.00636  1.43508  25  good
chromium@432510  2.17473  1.88215  25  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 666400

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests thread_times.simple_mobile_sites
Test Metric: thread_GPU_cpu_time_per_frame/thread_GPU_cpu_time_per_frame
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1821
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995271733204746992


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6383377752522752

| 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 Tests>AutoBisect.  Thank you!

Comment 7 by simonhatch@chromium.org, Nov 29 2016

Blockedon: 669608
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jan 13 2017

Cc: aelias@chromium.org
Owner: aelias@chromium.org

=== Auto-CCing suspected CL author aelias@chromium.org ===

Hi aelias@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : aelias
  Commit : eb9ecefc55d1e3cf8498d0865568097fb9bbf285
  Date   : Wed Nov 16 06:29:13 2016
  Subject: Revert "Getting rid of DelegatedFrameData"

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame
  Change       : 6.70% | 1.61052507368 -> 1.71839434963

Revision             Result                     N
chromium@432384      1.61053 +- 0.0230214       6      good
chromium@432389      1.60459 +- 0.0166774       6      good
chromium@432390      1.73306 +- 0.0252382       6      bad       <--
chromium@432391      1.73288 +- 0.00639238      6      bad
chromium@432393      1.7117 +- 0.0250757        6      bad
chromium@432401      1.72082 +- 0.0246551       6      bad
chromium@432418      1.71839 +- 0.0159729       6      bad

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 thread_times.simple_mobile_sites

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

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


| 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 Tests>AutoBisect.  Thank you!

Comment 10 by aelias@chromium.org, Jan 13 2017

Status: WontFix (was: Untriaged)
That's a revert, so the performance should come back on the reland.

Comment 11 by benhenry@chromium.org, Mar 14 2017

Labels: Performance-Memory
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Apr 10 2017 


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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                 N
chromium@432309      145310 +- 16991.8      21      good
chromium@432341      146806 +- 13287.3      21      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.m.youtube.com.results.q.science memory.top_10_mobile_stress

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

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


| 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 15 by 42576172...@developer.gserviceaccount.com, Apr 11 2017 


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

Bisect Details
  Configuration: android_nexus9_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_browser_cpu_time_per_frame/thread_browser_cpu_time_per_frame

Revision             Result                  N
chromium@432384      1.61786 +- 1.1875       25      good
chromium@432418      1.72885 +- 1.53439      25      bad

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 thread_times.simple_mobile_sites

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

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


| 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!
►

Sign in to add a comment