New issue
Advanced search Search tips

Issue 908031 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Closed: Nov 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

37%-50.1% regression in v8.browsing_desktop at 608701:608743

Project Member Reported by mlippautz@chromium.org, Nov 23

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/13a1e813e40000
Cc: oysteine@google.com
Owner: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/133c458fe40000

Perfetto: Add an upper bound to number of events per proto message by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/044129ce84b4e0ea59aaab9398fc9c76b51ae8d2
v8-gc-total: 225.2 → 314.8 (+89.69)

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

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

Sign in to add a comment