New issue
Advanced search Search tips

Issue 650687 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 650610
Owner:
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.9% regression in sunspider at 420831:420837

Project Member Reported by rmcilroy@chromium.org, Sep 27 2016

Issue description

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 27 2016

Mergedinto: 650610
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : Revert of [api] Clean up scopes and precheck instantiations cache (patchset #3 id:40001 of https://codereview.chromium.org/2206773003/ )
Author  : cbruni
Commit description:
  
Reason for revert:
Regresses API see go/v8-startup-api

Original issue's description:
> [api] Clean up scopes and precheck instantiations cache
>
> Make sure all the scopes used in api-natives.cc have inlineable constructors
> and destructors. Additionally directly precheck the instantiations cache before
> trying to enter the InvokeScope which sets the save_context.
>
> BUG=chromium:630217
>
> Committed: https://crrev.com/a2496b942cad524f0f3144b107936eaa9a7c9fd5
> Cr-Commit-Position: refs/heads/master@{#38346}

TBR=yangguo@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=chromium:630217,  chromium:635912 

Review-Url: https://codereview.chromium.org/2366903003
Cr-Commit-Position: refs/heads/master@{#39680}
Commit  : 85575cd8ee33fa3dd49ffc58de6e0b958df29094
Date    : Fri Sep 23 16:01:35 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@420830                1663.0   7.44983  5  good
chromium@420830,v8@84145a149b  1661.2   12.276   5  good
chromium@420830,v8@73518a9070  1658.63  10.3086  8  good
chromium@420830,v8@76eb976a67  1665.63  20.3536  8  good
chromium@420830,v8@12918397b4  1660.6   9.60729  5  good
chromium@420830,v8@85575cd8ee  1705.2   6.76018  5  bad    <--
chromium@420831                1710.2   14.1492  5  bad
chromium@420832                1714.4   8.70632  5  bad
chromium@420834                1715.2   10.3537  5  bad
chromium@420837                1722.8   20.584   5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 650687

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests sunspider
Test Metric: Total/Total
Relative Change: 3.60%
Score: 99.9

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


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

| 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