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

Issue 855410 link

Starred by 1 user
Status: WontFix
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

92.1% regression in thread_times.key_silk_cases at 568538:568621

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

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


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

android-webview-nexus5X
Project Member

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

GPU: Don't flush when destroying transfer buffers. by jdarpinian@chromium.org
https://chromium.googlesource.com/chromium/src/+/d1b4ae2892b05cf622b3f649cb38b995ed2d1733
0.003054 → 0.006124 (+0.003071)

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

Comment 4 by jdarpinian@chromium.org, Jun 25 2018

Status: WontFix (was: Assigned)
Although large percentage wise, this regression is tiny in absolute terms. An extra 0.003 milliseconds is not an issue.
►

Sign in to add a comment