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

Issue 910206 link

Starred by 1 user
Status: Assigned
Owner:
█ alexclarke@chromium.org
Last visit > 30 days ago
Cc:
liberato@google.com
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

18.8% regression in media_perftests at 611889:611954

Project Member Reported by liberato@google.com, Nov 29 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 29 

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

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


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

linux-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 29

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

Use the SequenceManager in ScopedTaskEnvironment by alexclarke@chromium.org
https://chromium.googlesource.com/chromium/src/+/514c49d40b386bd0fc3e544257ef2ec13e458028
clockless_playback: 1.573e+04 → 1.282e+04 (-2915)

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

Sign in to add a comment