New issue
Advanced search Search tips

Issue 610258 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

27.1% regression in webrtc.datachannel at 391555:391604

Project Member Reported by alexclarke@chromium.org, May 9 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=610258

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtMSXtwoM


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

chromium-rel-win7-gpu-ati
Trying a wider bisect.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Blink>WebRTC
Labels: -performance-sheriff Performance-Sheriff
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 11 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: asapersson@chromium.org
assigning to this weeks performance sheriff to take another look. Looking at the graphs it looks like a new "stable level" has been reached, not sure if that's to be expected due to some change.
Labels: -Performance-Sheriff
Is this still a valid issue?
Ping.
Status: Archived (was: Assigned)

Sign in to add a comment