New issue
Advanced search Search tips

Issue 808627 link

Starred by 1 user
Status: Duplicate
Owner:
rmcilroy@chromium.org
Closed: Mar 2018
Cc:
npm@chromium.org
rmcilroy@chromium.org
mstarzinger@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.6%-5.3% regression in jetstream with bytecode operand poisoning

Project Member Reported by npm@chromium.org, Feb 2 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 2 2018 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=49d160542ea3d9afeb0b82895c4857ecdfaf787dd39af6296c9d217218fa3462


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

android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
linux-release
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 3 2018

Cc: mstarzinger@chromium.org rmcilroy@chromium.org
Owner: rmcilroy@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14c0e701840000

[Intepreter] Add poisoning to bytecode operand reads. by rmcilroy@chromium.org
v8 @ c9941af275e5149b3d67cf2ba3897e26c85874e0

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by rmcilroy@chromium.org, Mar 20 2018

Mergedinto: 798964
Status: Duplicate (was: Assigned)

Comment 5 by rmcilroy@chromium.org, Mar 20 2018

Mergedinto: -798964 799400
Summary: 2.6%-5.3% regression in jetstream with bytecode operand poisoning (was: 2.6%-5.3% regression in jetstream at 532406:532672)
►

Sign in to add a comment