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

Issue 856205 link

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



Sign in to add a comment

4.3%-9.3% regression in power.desktop at 566810:567103

Project Member Reported by perezju@google.com, Jun 25 2018 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-nvidia
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 25 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/1394688f240000

presentation feedback: Use a GLFence fallback. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/3821fdf5c54add24d02adef248a311c293ea0bd0
0.1231 → 0.1271 (+0.004005)

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

Sign in to add a comment