New issue
Advanced search Search tips

Issue 872129 link

Starred by 1 user
Status: WontFix
Owner:
keishi@chromium.org
Closed: Aug 21
Cc:
mlippautz@chromium.org
keishi@chromium.org
haraken@chromium.org
toyoshim@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.2% regression in system_health.memory_mobile at 579727:579750

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

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

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

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


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

Android Nexus5X WebView Perf
Project Member

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

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

Oilpan: Enable incremental marking by default by keishi@chromium.org
https://chromium.googlesource.com/chromium/src/+/d92ab8be365f7c52d1ead03f2d2f3a75510957f3
5.271e+07 → 5.377e+07 (+1.061e+06)

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

Comment 4 by keishi@chromium.org, Aug 10

Cc: mlippautz@chromium.org haraken@chromium.org
Components: Blink>MemoryAllocator>GarbageCollection
Incremental marking related.
All other benchmarks including browse_news_washingtonpost do not show a regression so I think the effect is limited and justified for this change.
https://chromeperf.appspot.com/report?sid=f19d4896736a0e6a5b65fa52aa3c4c3aa36bcb543353675220465db4f0a4c9d4&rev=579750

Comment 5 by keishi@chromium.org, Aug 21

Status: WontFix (was: Assigned)
►

Sign in to add a comment