From: Clemens Ladisch <clemens@ladisch.de>
To: Adam Rosenberg <adam@alcorn.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA processor usage is too high
Date: Fri, 05 Nov 2010 15:31:04 +0100 [thread overview]
Message-ID: <4CD41528.1060600@ladisch.de> (raw)
In-Reply-To: <AANLkTik-sb1OihaDhNgptH44gQ4__E+ozxhSKpA9GdSK@mail.gmail.com>
Adam Rosenberg wrote:
> I am trying to decode 8 MP3 files simultaneously. Each file is 3
> minutes 11 seconds long. When I just decode the files and copy the
> PCM data to memory it takes 2 minutes 36 seconds. When I do the same
> test after opening 8 ALSA PCM streams and while writing data to them
> it takes 4 minutes 37 seconds. This is much too slow for what should
> be a simple copy operation.
Are you using the "hw" device? Otherwise, it's not a simple copy op.
How much CPU does "aplay -D hw -t raw -f dat /dev/zero" use?
Regards,
Clemens
next prev parent reply other threads:[~2010-11-05 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 14:12 ALSA processor usage is too high Adam Rosenberg
2010-11-05 14:31 ` Clemens Ladisch [this message]
2010-11-05 15:19 ` Adam Rosenberg
2010-11-05 17:58 ` Clemens Ladisch
2010-11-05 18:45 ` Adam Rosenberg
2010-11-05 18:51 ` Mark Brown
2010-11-05 19:10 ` Clemens Ladisch
2010-11-05 19:27 ` Adam Rosenberg
2010-11-06 5:30 ` Mark Brown
2010-11-08 10:39 ` Clemens Ladisch
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=4CD41528.1060600@ladisch.de \
--to=clemens@ladisch.de \
--cc=adam@alcorn.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 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.