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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_8jTqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_8ywrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv8_5oQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv5WbvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA_7KqtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv5_ssQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv9XDtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAv7HMvgoM


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

webrtc-android-tests-nexus5
webrtc-linux-large-tests
webrtc-mac-large-tests
webrtc-win-large-tests

The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f

commit d72595eeea4812f33bc7e23ec4c2bfcc99adac2f
Author: henrik.lundin <henrik.lundin@webrtc.org>
Date: Thu Mar 10 10:26:29 2016

Fix NetEq performance test regression

The test code created an AudioBuffer object inside the work loop. This
turned out to be expensive, since the AudioBuffer ctor implicitly
called memset on all of the audio data array. The obvious remedy is to
create the buffer outside of the loop. This does not have any impact
apart from the performance boost, since the output data from NetEq is
not even considered in the test.

BUG= chromium:592907 , webrtc:5647 
TBR=ivoc@webrtc.org
NOTRY=true

Review URL: https://codereview.webrtc.org/1782803002

Cr-Commit-Position: refs/heads/master@{#11940}

[modify] https://crrev.com/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f/webrtc/modules/audio_coding/neteq/tools/neteq_performance_test.cc
[modify] https://crrev.com/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f/webrtc/modules/include/module_common_types.h

All graphs have recovered with the fix in #5.