New issue
Advanced search Search tips

Issue 915069 link

Starred by 1 user
Status: Duplicate
Owner:
samans@chromium.org
Closed: Dec 20
Cc:
samans@chromium.org
benhenry@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

221.1% regression in memory.desktop at 615598:615780

Project Member Reported by benhenry@google.com, Dec 14 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 14 

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

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


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

Win 7 Nvidia GPU Perf

memory.desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 19

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

Use SharedImage in WebGL's DrawingBuffer by samans@chromium.org
https://chromium.googlesource.com/chromium/src/+/bce53252ce5ded76582c9a27a499bda2249052fc
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 3.62e+06 → 1.157e+07 (+7.954e+06)

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

Benchmark documentation link:
  None

Comment 4 by samans@chromium.org, Dec 20

Mergedinto: 914543
Status: Duplicate (was: Assigned)
►

Sign in to add a comment