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

Issue 677400 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2% regression in system_health.memory_mobile at 439253:439327

Project Member Reported by alexclarke@chromium.org, Dec 29 2016

Issue description

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 29 2016

Mergedinto: 675525
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : PreParsing inner functions: Make inner functions less lazy.
Author  : marja
Commit description:
  
Especially, make non-declaration type inner functions eagerly
parsed. Then we still have a chance to compile them eagerly if we see ()
after the function.

BUG= v8:5501 

Review-Url: https://codereview.chromium.org/2583843002
Cr-Commit-Position: refs/heads/master@{#41762}
Commit  : f37d726435d3f491dbd193c8c126ebf2252a0212
Date    : Fri Dec 16 13:34:30 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N   Good?
chromium@439252                4217443  88067.0  14  good
chromium@439257                4202685  29832.6  6   good
chromium@439260                4211400  49764.3  6   good
chromium@439260,v8@63279611b2  4205209  14444.9  6   good
chromium@439260,v8@d2d6da0354  4220501  72937.2  9   good
chromium@439260,v8@f37d726435  4289211  80496.7  6   bad    <--
chromium@439260,v8@16fe426320  4302905  67058.8  6   bad
chromium@439261                4266281  10614.0  6   bad
chromium@439262                4270741  9902.96  6   bad
chromium@439271                4286717  66169.1  6   bad
chromium@439290                4277203  72057.2  9   bad
chromium@439327                4271224  39859.5  9   bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 677400

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.ebay system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_ebay
Relative Change: 1.28%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4485
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991949578355330128


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

| 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