New issue
Advanced search Search tips

Issue 915626 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.6% regression in speedometer2 at 614502:614636

Project Member Reported by tebbi@chromium.org, Dec 17

Issue description

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

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


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

Win 7 Perf

speedometer2 - Benchmark documentation link:
  None
Components: -Blink
Cc: u...@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1020371e140000

[heap] Support concurrent marking of code objects. by ulan@chromium.org
https://chromium.googlesource.com/v8/v8/+/b04632d58166747d6e2385c441cb2bcf48f2ce3d
Vanilla-ES2015-TodoMVC: 224.4 → 233.4 (+9.039)

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

Benchmark documentation link:
  None
Owner: u...@chromium.org

Sign in to add a comment