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

Issue 855467 link

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



Sign in to add a comment

1.8% regression in system_health.memory_desktop at 566810:567068

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=855467

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


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

chromium-rel-win10
Project Member

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

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

presentation feedback: Use a GLFence fallback. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/3821fdf5c54add24d02adef248a311c293ea0bd0
5.429e+08 → 5.542e+08 (+1.133e+07)

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

Comment 4 by benhenry@chromium.org, Aug 2

Components: Speed>Metrics>SystemHealthRegressions

Comment 5 by benhenry@chromium.org, Aug 2

Components: -Speed>Metrics>SystemHealthRegressions
►

Sign in to add a comment