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

Issue 903104 link

Starred by 1 user
Status: Assigned
Owner:
herb@google.com
Cc:
█ alexclarke@chromium.org
herb@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-2.3% regression in system_health.memory_mobile at 600257:600303

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

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

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 8

Cc: herb@google.com
Owner: herb@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/119ffa2be40000

Reland "Have GrAtlasManager use legacy behavior" by herb@google.com
https://skia.googlesource.com/skia/+/bbf5fb5be451174f8a3671927a263069e1a02853
memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size: 1.54e+07 → 1.573e+07 (+3.356e+05)

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

Benchmark documentation link:
  None
►

Sign in to add a comment