New issue
Advanced search Search tips

Issue 837173 link

Starred by 1 user
Status: WontFix
Owner:
lukasza@chromium.org
Closed: Apr 2018
Cc:
pastarmovj@chromium.org
mlippautz@chromium.org
rdevlin....@chromium.org
isherman@chromium.org
lukasza@chromium.org
alex...@chromium.org
wfh@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 838940



Sign in to add a comment

5.2%-160.7% regression in v8.browsing_desktop at 552591:552602

Project Member Reported by mlippautz@chromium.org, Apr 26 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 26 2018 

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

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


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

chromium-rel-mac11-air
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 26 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15469419c40000
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 27 2018

Cc: kbr@chromium.org rdevlin....@chromium.org alex...@chromium.org lukasza@chromium.org pastarmovj@chromium.org isherman@chromium.org
Owner: lukasza@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16f012c5c40000

Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org
https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd

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

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 27 2018 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14158885c40000

Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org
https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd

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

Comment 8 by lukasza@chromium.org, Apr 27 2018

Components: Internals>Sandbox>SiteIsolation
Status: WontFix (was: Assigned)
Both #c6 and #c7 seems to report a regression in memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size

This regression is expected - it is expected that site-per-process uses more memory - on average we expect to increase memory usage (e.g. as measured by Memory.Total.PrivateMemoryFootprint) by around 10%.

Comment 9 by lukasza@chromium.org, May 2 2018

Blocking: 838940

Comment 10 by kbr@chromium.org, May 2 2018

Cc: -kbr@chromium.org
►

Sign in to add a comment