New issue
Advanced search Search tips

Issue 912011 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 913553
Owner:
Closed: Dec 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.4% regression in dromaeo at 613516:613545

Project Member Reported by toyoshim@chromium.org, Dec 5

Issue description

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

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


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

linux-perf

dromaeo - Benchmark documentation link:
  None
Status: Available (was: Untriaged)
Status: Untriaged (was: Available)
Cc: jgruber@chromium.org
Owner: jgruber@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13af0f9c140000

[nojit] Refactor CallApiCallback calling convention by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/c6b0e12e4e664d82cdbbfddca273546b82f98f5d
dom: 1.604e+06 → 1.436e+06 (-1.679e+05)

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

Benchmark documentation link:
  None
Mergedinto: 913553
Status: Duplicate (was: Assigned)

Sign in to add a comment