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

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


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

chromium-webrtc-trunk-tot-rel-win7

All alerts:
https://chromeperf.appspot.com/alerts?sheriff=WebRTC%20Statistics%20Perf%20Sheriff&sortby=end_revision&sortdirection=down

461163 - 461177 ChromiumWebRTCFYI chromium-webrtc-trunk-tot-rel-mac   browser_tests getStats_callback/invocation_time   54.1%     0.705 ms
469429 - 469432 ChromiumWebRTC    chromium-webrtc-rel-mac             browser_tests getStats_promise/invocation_time    48.7%     0.573 ms
469446 - 469462 ChromiumWebRTCFYI chromium-webrtc-trunk-tot-rel-mac   browser_tests getStats_callback/invocation_time   44.7%     0.603 ms
482013 - 482037 ChromiumWebRTCFYI chromium-webrtc-trunk-tot-rel-mac   browser_tests getStats_callback/invocation_time   62.8%     0.875 ms
495159 - 495170 ChromiumWebRTCFYI chromium-webrtc-trunk-tot-rel-win7  browser_tests getStats_promise/invocation_time    3687.7%   46.834 ms
495185 - 495218 ChromiumWebRTCFYI chromium-webrtc-trunk-tot-rel-win8  browser_tests getStats_callback/invocation_time   5652.0%   81.813 ms

Did something happen to the bots? I don't see any recent changes to the stats collectors but there could be changes to the lower layer components. Windows is taking a much greater hit than anything else.

The invocation time on windows would break apps frequently calling getStats.

Yes, see https://groups.google.com/a/google.com/d/msg/webrtc-perf-sheriffs/4J9XcGQN5Wo/4Y8hklDzAAAJ

Awesome, I'll wait and see if it goes down.

These are back to normal now :)