New issue
Advanced search Search tips

Issue 661064 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

4.3% regression in sunspider at 428688:428695

Project Member Reported by kouhei@google.com, Nov 1 2016

Issue description

See the link to graphs below.
 

Comment 1 by kouhei@google.com, Nov 1 2016

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

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


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

chromium-rel-win8-dual
Cc: mstarzinger@chromium.org
Owner: mstarzinger@chromium.org

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

Hi mstarzinger@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 : [compiler] Ship Ignition for all TurboFan code.
Author  : mstarzinger
Commit description:
  
This enables Ignition unconditionally for all code that is destined for
optimization with TurboFan. This ensures all optimization attempts will
go through the BytecodeGraphBuilder and that the AstGraphBuilder pipe is
dried out in practice.

patch from issue 2427953002 at patchset 120001 (http://crrev.com/2427953002#ps120001)

R=mvstanton@chromium.org,rmcilroy@chromium.org

Review-Url: https://codereview.chromium.org/2453973004
Cr-Commit-Position: refs/heads/master@{#40663}
Commit  : b4b436de6ad42e83d259418965a1a62c540a9fc7
Date    : Mon Oct 31 09:43:43 2016


===== TESTED REVISIONS =====
Revision                       Mean   Std Dev   N  Good?
chromium@428687                202.0  1.22474   5  good
chromium@428691                201.8  1.92354   5  good
chromium@428693                200.4  0.547723  5  good
chromium@428693,v8@b4b436de6a  206.8  0.447214  5  bad    <--
chromium@428693,v8@174da467ec  207.4  0.894427  5  bad
chromium@428694                206.8  0.83666   5  bad
chromium@428695                206.8  0.83666   5  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 661064

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests sunspider
Test Metric: Total/Total
Relative Change: 2.38%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2267
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997225079659562784


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

| 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: rmcilroy@chromium.org
Status: Assigned (was: Untriaged)
Mergedinto: 661556
Status: Duplicate (was: Assigned)

Sign in to add a comment