All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: pulseaudio eats 19% CPU power in Fedora 12
Date: Wed, 21 Apr 2010 08:57:28 +0100	[thread overview]
Message-ID: <hqmb58$frb$1@dough.gmane.org> (raw)
In-Reply-To: <u2l4f3252891004201730g94e709abs8ebf34b00d9ed505@mail.gmail.com>

'Twas brillig, and Raymond Yau at 21/04/10 01:30 did gyre and gimble:
> 2010/4/19 Daniel Chen <seven.steps@gmail.com>
> 
>>  but, like
>> Lennart suggests, these are by no means *caused* by PulseAudio.
>>
>> Best,
>> -Dan
>>
>>
> There are other factor affecting CPU usage  significantly
> 
> 1) the number of pulseaudio clients connected to PA server (i.e. number of
> audio stream need to be mixed )
> 2) the accuracy of system timer and the clock of the sound chip
> 3) the latency requirement of the different PA clients
> 4) the resampling method
> 5) the cpu loading of the system
> 6) the period time/period size selected by PA server to configure the alsa
> driver
> 
> why do you ruled out the cause ?
> 
>>> If you use "pacat" you can play audio with almost zero CPU
> usage
> 
> do you get the zero CPU usage in  Ubuntu 9.04/Ubuntu 9.10 with pacat on your
> machines ?

The pacat support for proper latency adjustment is only available in
more recent PA versions (with some , so chances are the older distros
wont have them (although I believe a 9.10 version of 0.9.21+stable-queue
exists somewhere.


These commits from stable-queue are certainly needed:

commit 19fa81bf1375032cb1a27c7715a28a52b238d4cb
Author: Lennart Poettering <lennart@poettering.net>
Date:   Thu Feb 18 01:54:51 2010 +0100

    pacat: always fully fulfill write requests

    Make sure we always fulfill write requests from the server. If we don't
    the server won't ask us again and playback will stay stuck.


https://tango.0pointer.de/pipermail/pulseaudio-discuss/2010-February/006611.html


and this one (although it's not problematic for playback):

commit b2e9fb6f6e12a3eab8a41c67017507e60d616e2a
Author: Lennart Poettering <lennart@poettering.net>
Date:   Sun Feb 21 21:09:26 2010 +0100

    pacat: pass buffer_attr to recording streams too

    Pointed out by Colin Guthrie.


https://tango.0pointer.de/pipermail/pulseaudio-discuss/2010-February/006698.html






-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mandriva Linux Contributor [http://www.mandriva.com/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

  reply	other threads:[~2010-04-21  7:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  7:56 pulseaudio eats 19% CPU power in Fedora 12 Wu Fengguang
2010-04-14  8:31 ` Colin Guthrie
2010-04-19  3:28 ` Lennart Poettering
2010-04-19  3:38   ` [alsa-devel] " Daniel Chen
2010-04-21  0:30     ` Raymond Yau
2010-04-21  7:57       ` Colin Guthrie [this message]
2010-04-22  1:11         ` Raymond Yau
2010-04-22  7:53           ` Colin Guthrie
2010-04-19  5:20   ` Shuang He
2010-04-19 14:48     ` [pulseaudio-discuss] " Lennart Poettering
2010-04-20  3:30       ` Raymond Yau
2010-04-19  8:34   ` Raymond Yau
2010-04-20  5:36   ` Raymond Yau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hqmb58$frb$1@dough.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.