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

Issue 799981 link

Starred by 1 user
Status: Fixed
Owner:
geoffl...@chromium.org
Closed: Feb 2018
Cc:
geoffl...@chromium.org
benjhayden@chromium.org
dtu@chromium.org
tdres...@chromium.org
pnoland@google.com
zmo@chromium.org
█ rkaplow@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

20.2%-592.3% regression in thread_times.tough_scrolling_cases at 527322:527481

Project Member Reported by benjhayden@chromium.org, Jan 8 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 8 2018 

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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 8 2018 

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 9 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12e6277b040000

Comment 6 by benjhayden@chromium.org, Jan 9 2018

Cc: dtu@chromium.org pnoland@google.com tdres...@chromium.org
Owner: pav...@chromium.org
Status: Assigned (was: Untriaged)
pavely: Pinpoint identified "[Sync] Don't encrypt specifics of tombstone commit" as the culprit of a regression in thread_total_all_cpu_time_per_frame. See the dashboard charts:
https://chromeperf.appspot.com/group_report?bug_id=799981
https://chromium.googlesource.com/chromium/src/+/3db22d82a254b352b6dffb8968295578b4ea759e

+tdresser as owner of thread_times.tough_scrolling_cases
+pnoland as reviewer of the CL.

dtu: Just wanted to make sure you saw the gitiles 429 error in #5.

Comment 7 by dtu@chromium.org, Jan 9 2018 

Sorry, that is not the right culprit. Would you mind retrying the Pinpoint job?
(We have a bug for the 429 error: https://github.com/catapult-project/catapult/issues/4114#issuecomment-353687601)

Comment 8 by benjhayden@chromium.org, Jan 10 2018

Owner: ----
Status: Untriaged (was: Assigned)
Oops, thanks, Dave.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Jan 10 2018 

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

Comment 12 by 42576172...@developer.gserviceaccount.com, Jan 11 2018

Cc: zmo@chromium.org geoffl...@chromium.org rkaplow@chromium.org
Owner: geoffl...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16aa7417040000

Add fieldtrial testing for DefaultPassthroughCommandDecoder.
By geofflang@chromium.org · Fri Jan 05 18:11:20 2018
chromium @ 408921af86e70591ea6f05722e49babb6711ef23

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

Comment 13 by geoffl...@chromium.org, Feb 2 2018

Status: Fixed (was: Assigned)
►

Sign in to add a comment