mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Keith Chew" <keith.chew@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Performance bttv versus sharedmem
Date: Wed, 3 Jan 2007 08:44:24 +1300	[thread overview]
Message-ID: <20f65d530701021144p2df613dbvd5fe654ffcd09f91@mail.gmail.com> (raw)

Hi

This is just a general question to understand where the improvement
can be made.

In the first setup, I have these processes:
- mencoder recording from bttv chip at 8 fps (cpu 3.5 %)
- mplayer playing from bttv chip at 10 fps (cpu 2.1 %)

In the second setup, I have these processes:
- mencoder recording from bttv to shared mem at 25 fps (cpu 1.7%)
- mencoder recording from shared mem at 8 fps (cpu 6.1%)
- mplayer playing from shared mem at 10 fps (cpu 3.1 %)

For the shared mem setup, the access to the memory is efficient, only
a memcopy to a buffer. Are the CPU usages inline with what you'd
expect, that the shared mem being almost 2 times the CPU usage? How
can I reduce the CPU usage in the shared mem setup?

Regards
Keith

                 reply	other threads:[~2007-01-02 19:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20f65d530701021144p2df613dbvd5fe654ffcd09f91@mail.gmail.com \
    --to=keith.chew@gmail.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome