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

Issue 600291 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.1% regression in blink_perf.parser at 383957:383975

Project Member Reported by toyoshim@chromium.org, Apr 4 2016

Issue description

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

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


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

android-galaxy-s5
Cc: keishi@chromium.org
Owner: keishi@chromium.org

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

Hi keishi@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Introduce ProcessHeap
Author  : keishi
Commit description:
  
ProcessHeap is in charge of global BlinkGC heap state.

BUG= 591606 

Review URL: https://codereview.chromium.org/1842803003

Cr-Commit-Position: refs/heads/master@{#383965}
Commit  : 8d95071b1fb8ead8d041946bd781f9df10aea322
Date    : Wed Mar 30 13:37:12 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@383956         41.277105   0.376213    8           good
chromium@383961         39.992937   1.690897    8           good
chromium@383964         40.077433   0.487051    5           good
chromium@383965         37.274473   2.504943    5           bad         <-
chromium@383966         38.383209   0.446687    8           bad
chromium@383975         37.027603   0.214552    5           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 600291

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_perf.parser
Test Metric: query-selector-all-attribute/query-selector-all-attribute
Relative Change: 10.01%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/566
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016317978677105392


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

| 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!
Cc: nyerramilli@chromium.org
Labels: TE-Triaged
based on bisect results in c#2, keishi@ could you please check the issue.
Cc: ashej...@chromium.org
@keishi: Gentle Ping! Hey, would you mind checking the above issue as per comment#2 ?

Appreciate your help.

Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 20 2016


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

Hi keishi@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Introduce ThreadHeapStats
Author  : keishi
Commit description:
  
ThreadHeapStats collect stats about the Heap.

BUG= 591606 

Review URL: https://codereview.chromium.org/1840103004

Cr-Commit-Position: refs/heads/master@{#384275}
Commit  : bc43ce961dc073b71d35aa00cdeb174f81c7f8eb
Date    : Thu Mar 31 14:44:19 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@383956         39.518138   0.299238    5           good
chromium@384122         37.035134   0.477517    5           good
chromium@384206         35.95638    0.426066    5           good
chromium@384248         34.16785    0.334254    5           good
chromium@384269         33.650566   0.326711    5           good
chromium@384272         33.777203   0.307505    5           good
chromium@384274         33.751877   0.117428    5           good
chromium@384275         31.290881   1.039747    5           bad         <-
chromium@384280         32.221854   0.238335    5           bad
chromium@384290         32.042092   0.199615    5           bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 600291

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.parser
Test Metric: query-selector-all-attribute/query-selector-all-attribute
Relative Change: 18.92%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/612
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014883502259055440


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

| 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 6 by keishi@chromium.org, Apr 27 2016

Status: WontFix (was: Assigned)
Could be true that my CL caused a regression  but other android bots do not show a regression so I'm marking this as WontFix.

Sign in to add a comment