New issue
Advanced search Search tips

Issue 893852 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

20.8% regression in v8.browsing_desktop at 596514:596584

Project Member Reported by m...@chromium.org, Oct 9

Issue description

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

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


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

Win 7 Perf

v8.browsing_desktop - Benchmark documentation link:
  None
Cc: sadrul@chromium.org
Owner: sadrul@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1044130ce40000

synthetic gesture: Allow high-frequency dispatch. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/581a728b2665c85e466408c2d53371abcb7f763e
console:error:all: 275.8 → 333.2 (+57.4)

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

Benchmark documentation link:
  None

Sign in to add a comment