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

Issue 836532 link

Starred by 1 user
Status: WontFix
Owner:
lukasza@chromium.org
Closed: May 2018
Cc:
pastarmovj@chromium.org
rdevlin....@chromium.org
isherman@chromium.org
█ briander...@chromium.org
lukasza@chromium.org
alex...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 838940



Sign in to add a comment

3% regression in system_health.memory_desktop at 552596:552599

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

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

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

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


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

chromium-rel-win8-dual
Project Member

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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, May 8 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/16c1750fc40000

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 8 2018

Blocking: 838940
Status: WontFix (was: Assigned)
I see that the pinpoint job from #c5 tracks memory:chrome:all_processes:reported_by_chrome:malloc:effective_size.  Therefore, I think we can resolve the current bug as WontFix - 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 7 by kbr@chromium.org, May 9 2018

Cc: -kbr@chromium.org
►

Sign in to add a comment