Fix NetEq performance test regression

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

Committed: https://crrev.com/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f
Cr-Commit-Position: refs/heads/master@{#11940}

[hlundin-webrtc, 2016-03-10 10:08:06]

Description was changed from

==========
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
==========

to

==========
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
==========

[hlundin-webrtc, 2016-03-10 10:24:50]

The CQ bit was checked by henrik.lundin@webrtc.org

[commit-bot: I haz the power, 2016-03-10 10:24:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1782803002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1782803002/1

[commit-bot: I haz the power, 2016-03-10 10:26:32]

Description was changed from

==========
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
==========

to

==========
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
==========

[commit-bot: I haz the power, 2016-03-10 10:26:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-10 10:26:42]

Description was changed from

==========
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
==========

to

==========
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

Committed: https://crrev.com/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f
Cr-Commit-Position: refs/heads/master@{#11940}
==========

[commit-bot: I haz the power, 2016-03-10 10:26:43]

Patchset 1 (id:??) landed as
https://crrev.com/d72595eeea4812f33bc7e23ec4c2bfcc99adac2f
Cr-Commit-Position: refs/heads/master@{#11940}