New issue
Advanced search Search tips

Issue 902850 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 29
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.9%-2.5% regression in memory.top_10_mobile at 600983:601056

Project Member Reported by lanwei@chromium.org, Nov 7

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=902850

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

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

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: dtseng@chromium.org khushals...@chromium.org
Owner: dtseng@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11b8966de40000

gpu: Fix raster implementation error for no flush result available query by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/da82bcce69bf5384435976a1945c9cb3270c5abb
memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size: 6.927e+07 → 7.082e+07 (+1.541e+06)

Change toggle button output by dtseng@chromium.org
https://chromium.googlesource.com/chromium/src/+/bd7d50d18ef4f83698e6fea3fe9d8cc3dd013751
memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size: 7.082e+07 → 7.133e+07 (+5.15e+05)

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

Benchmark documentation link:
  None
Owner: ----
Status: Available (was: Assigned)
Unlikely to be my change.
Looks like it got fixed right after. My change did affect timings around context idle state which affects cleaning up of gpu memory. But it got restored with this change: https://chromium.googlesource.com/chromium/src/+/e898b99eac0cf5db379cf8c7e216d772095a7448, which is in the range where the graph recovered. Started a bisect to confirm that the improvement was from this change.
Owner: khushals...@chromium.org
Status: Assigned (was: Available)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/169ef9efe40000

cc: Rate limit raster metric queries. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/e898b99eac0cf5db379cf8c7e216d772095a7448
memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size: 7.175e+07 → 7.039e+07 (-1.359e+06)

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

Benchmark documentation link:
  None
Status: Fixed (was: Assigned)
That was it.

Sign in to add a comment