New issue
Advanced search Search tips

Issue 808350 link

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



Sign in to add a comment

1.9%-7.1% regression in speedometer2 with bytecode operand poisioning

Project Member Reported by tebbi@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=808350

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


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

android-one
chromium-rel-mac-retina
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-x64-dual
linux-release
Project Member

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

Cc: rmcilroy@chromium.org mstarzinger@chromium.org
Owner: rmcilroy@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/168e710e840000

[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, Feb 5 2018

Mergedinto: 799400
Status: Duplicate (was: Assigned)
Summary: 1.9%-7.1% regression in speedometer2 with bytecode operand poisioning (was: 1.9%-7.1% regression in speedometer2 at 532435:532672)
►

Sign in to add a comment