New issue
Advanced search Search tips

Issue 665367 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.3%-3.3% regression in sunspider at 431541:431558

Project Member Reported by toyoshim@chromium.org, Nov 15 2016

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8_-fqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi-yEpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg87bdqgoM


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

chromium-rel-mac-retina
chromium-rel-win7-gpu-nvidia
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 15 2016

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 : [interpreter] Enable OSR for Ignition by default.
Author  : mstarzinger
Commit description:
  
This enables the on-stack replacement mechanism from Ignition bytecode
to TurboFan optimized code by default. The runtime profiler is now
allowed to arm OSR points in bytecode.

R=rmcilroy@chromium.org

Review-Url: https://codereview.chromium.org/2432413004
Cr-Commit-Position: refs/heads/master@{#40911}
Commit  : 0a94ef09d4fa77b9c6c72f9e3374bec372dbdeb9
Date    : Fri Nov 11 10:42:07 2016


===== TESTED REVISIONS =====
Revision                       Mean    Std Dev  N   Good?
chromium@431542                158.04  14.626   50  good
chromium@431548                157.72  15.9399  50  good
chromium@431551                158.72  21.1206  50  good
chromium@431553                157.74  20.1896  50  good
chromium@431553,v8@be360af21a  156.54  14.4368  50  good
chromium@431553,v8@0a94ef09d4  161.42  19.6515  50  bad    <--
chromium@431554                160.14  18.1113  50  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 665367

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1956
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995938989624705312


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

| 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
Labels: Proj-Ignition
Status: Assigned (was: Untriaged)
It looks like this recovered around https://codereview.chromium.org/2487483004. Dup of issue 661556 ? 
Status: Fixed (was: Assigned)

Sign in to add a comment