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

Issue 709358 link

Starred by 1 user
Status: WontFix
Owner:
█ ivoc@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Cc:
peah@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.7% improvement in webrtc_perf_tests at 17481:17482

Project Member Reported by peah@chromium.org, Apr 7 2017 
ivoc@: Could you please take a look?

Comment 1 by peah@chromium.org, Apr 7 2017 

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

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


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

webrtc-mac-large-tests

Comment 2 by ivoc@chromium.org, Apr 13 2017

Components: Blink>WebRTC>Audio
Status: WontFix (was: Assigned)
I can't find anything to explain these performance variations. It looks like some of the changes have drifted closer to their previous level, but I don't have an explanation for this. I think we should close this bug and monitor how often false alarms are triggered by these stats, and consider removing them if it's too often.
►

Sign in to add a comment