New issue
Advanced search Search tips

Issue 838440 link

Starred by 1 user
Status: WontFix
Owner:
lukasza@chromium.org
Closed: May 2018
Cc:
pastarmovj@chromium.org
rdevlin....@chromium.org
m...@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

34.5% regression in memory.desktop at 552594:552602

Project Member Reported by m...@chromium.org, May 1 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 1 2018 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 1 2018 

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

Comment 5 by 42576172...@developer.gserviceaccount.com, May 3 2018

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

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 6 by lukasza@chromium.org, May 3 2018

Blocking: 838940
Cc: -kbr@chromium.org -isherman@chromium.org
Components: Internals>Sandbox>SiteIsolation
Status: WontFix (was: Assigned)
I see that the pinpoint job in #c5 looks at memory:chrome:all_processes:reported_by_chrome:malloc:allocated_objects_size.  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%.
►

Sign in to add a comment