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

Issue 855561 link

Starred by 1 user
Status: Duplicate
Owner:
jdarpinian@chromium.org
Closed: Jun 2018
Cc:
jdarpinian@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

28.4% regression in system_health.memory_desktop at 568599:568660

Project Member Reported by alexclarke@chromium.org, Jun 22 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 22 2018 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 22 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/171a1453240000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jun 26 2018

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

GPU: Don't flush when destroying transfer buffers. by jdarpinian@chromium.org
https://chromium.googlesource.com/chromium/src/+/d1b4ae2892b05cf622b3f649cb38b995ed2d1733
4.919e+06 → 6.177e+06 (+1.258e+06)

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

Comment 6 by jdarpinian@chromium.org, Jun 30 2018

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

Sign in to add a comment