alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: pulseaudio eats 19% CPU power in Fedora 12
Date: Wed, 21 Apr 2010 08:30:09 +0800	[thread overview]
Message-ID: <u2l4f3252891004201730g94e709abs8ebf34b00d9ed505@mail.gmail.com> (raw)
In-Reply-To: <k2q604760771004182038n72eec9bdy77a9e4faf2152ee4@mail.gmail.com>

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 ?

  reply	other threads:[~2010-04-21  0:30 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 [this message]
2010-04-21  7:57       ` Colin Guthrie
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=u2l4f3252891004201730g94e709abs8ebf34b00d9ed505@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).