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

Issue 640530 link

Starred by 1 user
Status: Duplicate
Owner:
█ nikolaos@chromium.org
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 640915


Sign in to add a comment

3.5%-5.6% regression in speedometer at 413799:413853

Project Member Reported by nikolaos@chromium.org, Aug 24 2016 
See the link to graphs below.

Comment 1 by nikolaos@chromium.org, Aug 24 2016 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3vqpugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3o-hsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvryftAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3u2csgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvoL-vgoM


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

android-nexus7v2
chromium-rel-mac-retina
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 24 2016 


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@413827  725.876  8.81905  18  good
chromium@413830  722.073  10.5505  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 640530

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: EmberJS-TodoMVC/EmberJS-TodoMVC
Relative Change: 0.10%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1134
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003455013201410912


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

| 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 5 by 42576172...@developer.gserviceaccount.com, Aug 24 2016 


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@413826  725.138  5.18599  5  good
chromium@413845  729.482  5.80226  5  good
chromium@413848  720.066  8.11951  5  good
chromium@413849  724.918  10.7008  5  good
chromium@413850  751.232  7.48593  5  bad
chromium@413854  755.22   5.69431  5  bad
chromium@413863  750.768  4.71323  5  bad
chromium@413899  754.594  9.92182  5  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 640530

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: EmberJS-TodoMVC/EmberJS-TodoMVC
Relative Change: 4.06%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1135
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003428957789889840


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

| 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 sullivan@chromium.org, Aug 25 2016

Blockedon: 641133

Comment 7 by sullivan@chromium.org, Aug 25 2016

Blockedon: -641133 640915
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Aug 29 2016 


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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@413813  730.234  15.0841  18  good
chromium@413837  725.525  9.56271  18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 640530

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: EmberJS-TodoMVC/EmberJS-TodoMVC
Relative Change: 2.49%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1152
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002972195961840048


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

| 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 12 by 42576172...@developer.gserviceaccount.com, Aug 30 2016

Mergedinto: 641656
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : [heap] Tracer: Handle incremental marking scopes
Author  : mlippautz
Commit description:
  
Before this patch all tracing scopes in incremental marking would be reset
during a gc tracer start/stop cycle. This patch handles scopes the same way it
does other incremental marking metrics.

Also:
- Align finalization metric with regular marking metric.
- Smaller cleanups

BUG= chromium:639818 

Review-Url: https://codereview.chromium.org/2273673002
Cr-Commit-Position: refs/heads/master@{#38834}
Commit  : 7695642e2c7d893d300920ac0084905288f72859
Date    : Tue Aug 23 15:13:50 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@413826                717.184  5.45941  5  good
chromium@413847                719.308  8.17869  5  good
chromium@413849                717.782  8.43504  8  good
chromium@413849,v8@b305c7dfcb  717.935  9.98546  8  good
chromium@413849,v8@d99b2db1a8  715.633  4.60192  5  good
chromium@413849,v8@7695642e2c  747.871  10.547   5  bad    <--
chromium@413850                740.718  6.74364  5  bad
chromium@413852                748.435  12.9924  5  bad
chromium@413857                738.893  5.26123  5  bad
chromium@413867                746.044  9.07379  5  bad
chromium@413907                749.764  8.7188   5  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 640530

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: EmberJS-TodoMVC/EmberJS-TodoMVC
Relative Change: 4.54%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1542
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002949439302467376


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

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

Sign in to add a comment