New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 879471 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Sep 1
Cc:
mlippautz@chromium.org
█ rfbpb@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7%-3028.8% regression in v8.browsing_desktop at 586985:587067

Project Member Reported by mlippautz@chromium.org, Aug 31 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 31 

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

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


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

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

v8.browsing_desktop - Benchmark documentation link:
  None

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 31

Cc: rfbpb@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1654c1a3640000

Reland "[heap] Attempt to incorporate backing store counters into heap sizing and GC trigger stragery." by rfbpb@google.com
https://chromium.googlesource.com/v8/v8/+/eb164dbd0066a0078e58932563eeb5fdd2b8e6d6
1.312 → 10.89 (+9.576)

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

Comment 4 by mlippautz@chromium.org, Sep 1

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

Sign in to add a comment