New issue
Advanced search Search tips

Issue 836259 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 838940



Sign in to add a comment

1.8%-83.2% regression in system_health.memory_desktop at 552586:552591

Project Member Reported by mvstanton@google.com, Apr 24 2018

Issue description

Is this from --site-per-process?
 
Project Member

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

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

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


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

chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

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

Cc: kbr@chromium.org rdevlin....@chromium.org isherman@chromium.org alex...@chromium.org lukasza@chromium.org pastarmovj@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14869419c40000

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
Components: Internals>Sandbox>SiteIsolation
Status: WontFix (was: Assigned)
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%.
Blocking: 838940

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

Cc: -kbr@chromium.org

Sign in to add a comment