From: Lennart Poettering <mznyfn@0pointer.de>
To: General PulseAudio Discussion <pulseaudio-discuss@mail.0pointer.de>
Cc: "Fu, Michael" <michael.fu@intel.com>,
alsa-devel@alsa-project.org,
Wu Fengguang <fengguang.wu@intel.com>,
"Bu, Long" <long.bu@intel.com>
Subject: Re: [pulseaudio-discuss] pulseaudio eats 19% CPU power in Fedora 12
Date: Mon, 19 Apr 2010 16:48:34 +0200 [thread overview]
Message-ID: <20100419144832.GC1048@tango.0pointer.de> (raw)
In-Reply-To: <4BCBE81F.6090606@intel.com>
On Mon, 19.04.10 13:20, Shuang He (shuang.he@intel.com) wrote:
Please stop the cross-posting.
>
> current latency: 444.25 ms
> requested latency: 31.25 ms
So, this is interesting: the client requested 30ms (which is needlessly
low, but that's another question), but the server ended up providing
only 444 ms! That is incredibly high and points to the fact that PA
probably ran into quite a few dropouts before this, presumably due to
incorrect timing or suchlike, and hence bumped up the minimal latency
all the time, and bumped down the sleeping time, hence eincreasing the
CPU load. Almost certainly your audio driver is at fault here.
Check syslog for any comments about that.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2010-04-19 14:49 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
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 ` Lennart Poettering [this message]
2010-04-20 3:30 ` [pulseaudio-discuss] " 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=20100419144832.GC1048@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=long.bu@intel.com \
--cc=michael.fu@intel.com \
--cc=pulseaudio-discuss@mail.0pointer.de \
/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).