New issue
Advanced search Search tips

Issue 897082 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 19
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

46.6%-56.7% regression in memory:chrome:all_processes:reported_by_chrome:gpu:effective_size at 600107:600257

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 19

Issue description

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

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


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

Win 7 Nvidia GPU Perf

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: khushals...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/178ae57ae40000

Reland gpu: Add UMA metric for measuring total raster task duration. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/cd8fbb77cfa164eef66378204a588443af9bb875
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 2.449e+06 → 3.391e+06 (+9.417e+05)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 896260
Status: Duplicate (was: Assigned)

Sign in to add a comment