New issue
Advanced search Search tips

Issue 911055 link

Starred by 2 users
Status: Duplicate
Owner:
oysteine@google.com
Closed: Dec 3
Cc:
jgruber@chromium.org
oysteine@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

67.4% regression in v8.browsing_desktop at 608673:608700

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

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

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

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


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

mac-10_13_laptop_high_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None
Project Member

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

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/1588339fe40000

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: 76.6 → 102.6 (+26)

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

Benchmark documentation link:
  None

Comment 4 by oysteine@google.com, Dec 3

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

Sign in to add a comment