New issue
Advanced search Search tips

Issue 899634 link

Starred by 1 user
Status: Assigned
Owner:
neis@chromium.org
Cc:
jarin@chromium.org
neis@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.4%-20.2% regression in v8.browsing_desktop at 599580:599654

Project Member Reported by ulan@google.com, Oct 29 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 29 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf

v8.browsing_desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 29

Cc: neis@chromium.org
Owner: neis@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11b1c6f9e40000

Turn --concurrent_typed_lowering on by default. by neis@chromium.org
https://chromium.googlesource.com/v8/v8/+/b5e45a285b33da5a8025d5d8e90a656dbdac43eb
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size: 6.092e+07 → 7.184e+07 (+1.093e+07)

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

Benchmark documentation link:
  None

Comment 4 by neis@chromium.org, Nov 5

Cc: jarin@chromium.org
►

Sign in to add a comment