New issue
Advanced search Search tips

Issue 913552 link

Starred by 2 users
Status: Duplicate
Merged: issue 913553
Owner:
jgruber@chromium.org
Closed: Dec 11
Cc:
jgruber@chromium.org
npm@chromium.org
lfg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.1%-18.2% regression in blink_perf.bindings at 613466:613789

Project Member Reported by npm@chromium.org, Dec 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 10 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf
mac-10_13_laptop_high_end-perf

blink_perf.bindings - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 11

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/101dc7d2140000

[nojit] Refactor CallApiCallback calling convention by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/c6b0e12e4e664d82cdbbfddca273546b82f98f5d
undefined-first-child: 4581 → 4160 (-421)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Comment 4 by jgruber@chromium.org, Dec 11

Mergedinto: 913553
Status: Duplicate (was: Assigned)
►

Sign in to add a comment