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

Issue 805979 link

Starred by 1 user
Status: Assigned
Owner:
u...@chromium.org
Cc:
twelling...@chromium.org
█ nyquist@chromium.org
ssid@chromium.org
mlamouri@chromium.org
majidvp@chromium.org
u...@chromium.org
ofrobots@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-6.8% regression in system_health.memory_mobile at 531332:531461

Project Member Reported by majidvp@google.com, Jan 25 2018 
See the link to graphs below.
Project Member

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

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

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


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

android-nexus5
android-nexus5X
android-webview-nexus5X
Project Member

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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 27 2018 

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

Comment 8 by 42576172...@developer.gserviceaccount.com, Mar 3 2018

Cc: twelling...@chromium.org ssid@chromium.org nyquist@chromium.org
Owner: ssid@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13d8b7a4440000

Do not store favicon for all tabs in MediaSessionTabHelper by ssid@chromium.org
https://chromium.googlesource.com/chromium/src/+/f5d5e2e779a0cc6d6e128b5915b5facbbace201c

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

Comment 9 by 42576172...@developer.gserviceaccount.com, Mar 4 2018

Cc: ofrobots@google.com u...@chromium.org
Owner: ofrobots@google.com
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14b519bc440000

[heap] allocation step should before limit update by ofrobots@google.com
https://chromium.googlesource.com/v8/v8/+/95249bca1f473283c11b1a808e1a06767feeb899

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

Comment 10 by u...@chromium.org, Mar 5 2018

Owner: u...@chromium.org
I'll take a look.
Project Member

Comment 12 by 42576172...@developer.gserviceaccount.com, Mar 19 2018

Owner: ssid@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12f61a81440000

Do not store favicon for all tabs in MediaSessionTabHelper by ssid@chromium.org
https://chromium.googlesource.com/chromium/src/+/f5d5e2e779a0cc6d6e128b5915b5facbbace201c

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

Comment 13 by u...@chromium.org, Mar 19 2018

Owner: u...@chromium.org
There two regressions grouped into this bug.

Java memory regressions bisect to ssid's CL. I forked them to  crbug.com/823311

Comment 14 by mlamouri@chromium.org, Mar 21 2018

Cc: mlamouri@chromium.org
Owner: ssid@chromium.org
The original change was to reduce memory usage and if I understand correctly, we are actually regressing memory usage? Before taking another change on top of it that is going to increase complexity a bit more, can we look into the benefits of this and whether we are going in the right direction?

Comment 15 by ssid@chromium.org, Mar 21 2018

Owner: u...@chromium.org
Sorry. I reported the wrong bug number in the cl.
I have explained in Issue 806861.
Assigning this to ulan to look at the other regression.

Comment 16 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 17 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions
►

Sign in to add a comment