New issue
Advanced search Search tips

Issue 871401 link

Starred by 1 user
Status: Assigned
Owner:
sunn...@chromium.org
Cc:
sunn...@chromium.org
ericrk@chromium.org
chiniforooshan@chromium.org
primiano@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

19.6% regression in system_health.memory_mobile at 577263:577412

Project Member Reported by chiniforooshan@chromium.org, Aug 6 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 6 

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

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


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

android-nexus5x-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 7

Cc: sunn...@chromium.org
Owner: sunn...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12b42d68640000

Reland "cc: Throttle incoming begin frames in scheduler" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/1607d9124b4df6bf0175c3ec69b7aef6a981ddb6
4.077e+07 → 4.875e+07 (+7.979e+06)

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

Comment 4 by sunn...@chromium.org, Aug 8

Cc: primiano@chromium.org ericrk@chromium.org
Don't know what to do here. None of our memory metrics show a change, but according to the OS (probably adb dumpsys meminfo?), the gpu process is using more graphics memory.

+primiano@ ericrk@ in case they have any ideas
►

Sign in to add a comment