All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:58:21 +0100	[thread overview]
Message-ID: <4CD445BD.3020501@ladisch.de> (raw)
In-Reply-To: <AANLkTinXm2G1y477xRTc_QjXuEZ_nyAqGWuSkq32KGe2@mail.gmail.com>

Adam Rosenberg wrote:
> On Fri, Nov 5, 2010 at 10:31 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > How much CPU does "aplay -D hw -t raw -f dat /dev/zero" use?
> 
> I do not know how to calculate CPU usage for a given process.

The time utility (if you have it) measures both elapsed and actually
used CPU time.

> For the audio playback I am polling the streams using
> snd_pcm_avail_update() and then writing the number of frames available
> using snd_pcm_writei().

And what does your program do when avail_update returns 0 frames?

> I am able to add aplay for testing so I used your command to open the
> 8 streams, removed the audio processing from my application, and ran
> the test again.  The result was 4 minutes and 35 seconds, which is
> basically the same as the result from the test within my application
> and much too slow.

You cannot write data faster than it's playing; the audio ring buffer
has a finite size.

You would have a problem if the processing and/or the driver would
make everything so slow that you wouldn't be able to write new data
to the device fast enough, which would result in an buffer underrun.
Does this actually happen?


Regards,
Clemens

  reply	other threads:[~2010-11-05 17:56 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
2010-11-05 15:19   ` Adam Rosenberg
2010-11-05 17:58     ` Clemens Ladisch [this message]
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=4CD445BD.3020501@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.