diff options
| author | dalecurtis@chromium.org <dalecurtis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-17 06:06:45 +0000 |
|---|---|---|
| committer | dalecurtis@chromium.org <dalecurtis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-04-17 06:06:45 +0000 |
| commit | 64e0e3b22059b006a2119a14887901f287c9f35e (patch) | |
| tree | 129c9117a5d1e1abee5dc9d00c8d43ab48fb7e79 /content/renderer/media | |
| parent | f212ee13b64f6ced8d0948d51f7c1ac841ecc74d (diff) | |
| download | chromium_src-64e0e3b22059b006a2119a14887901f287c9f35e.zip chromium_src-64e0e3b22059b006a2119a14887901f287c9f35e.tar.gz chromium_src-64e0e3b22059b006a2119a14887901f287c9f35e.tar.bz2 | |
Use larger buffer sizes for lower power on Linux.
HTML5 playback on Linux ALSA, Pulse, and ChromeOS will now use a
buffer size of 1024+ for media playback.
On my Z620 this takes pulseaudio daemon CPU usage from a solid 3-4%
down to 1%. Likely there are savings in the Chrome process as well,
but those are harder to measure against process noise.
I suspect we'll see greater savings on Chromebooks.
BUG=362261
TEST=Audio sounds the same always. CPU usage down.
NOTRY=true
Review URL: https://codereview.chromium.org/235723003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264443 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/media')
| -rw-r--r-- | content/renderer/media/audio_renderer_mixer_manager.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/renderer/media/audio_renderer_mixer_manager.cc b/content/renderer/media/audio_renderer_mixer_manager.cc index 9fc2e59..935fe76 100644 --- a/content/renderer/media/audio_renderer_mixer_manager.cc +++ b/content/renderer/media/audio_renderer_mixer_manager.cc @@ -67,7 +67,7 @@ media::AudioRendererMixer* AudioRendererMixerManager::GetMixer( // know that works well for WebAudio and WebRTC. media::AudioParameters output_params( media::AudioParameters::AUDIO_PCM_LOW_LATENCY, params.channel_layout(), - sample_rate, 16, hardware_config_->GetOutputBufferSize()); + sample_rate, 16, hardware_config_->GetHighLatencyBufferSize()); // If we've created invalid output parameters, simply pass on the input params // and let the browser side handle automatic fallback. |