From: Chris Stanley <cstanley@cctv.org>
To: pthreads-win32@sourceware.org
Subject: Re: Max 50% usage on dual-core CPU
Date: Thu, 15 Nov 2007 19:22:00 -0000 [thread overview]
Message-ID: <4738B89C.9020207@cctv.org> (raw)
In-Reply-To: <4738B06B.20206@cctv.org>
I got a reply back from the other list and it was an ffmpeg issue with
an easy fix. Sorry for the bother, thanks!
--
Chris Stanley
Systems Administrator cstanley@cctv.org
Office 802-862-1645, x11
Center for Media & Democracy Mobile 802-324-8415
Fax 802-860-2370
294 North Winooski Ave IM ChrisStanleyCCTV
Burlington, VT 05401 http://www.cctv.org/
Chris Stanley wrote:
> I'm working with ffmpeg which uses Pthreads-w32 in Windows XP Pro SP2.
> I've used both Pthreads-w32 2.8.0 and 2.9.0 (which as far as I can tell
> doesn't exist, but is bundled with the Celtic Druid ffmpeg binaries
> nonetheless).
>
> When using a single-core system (Celeron 2.5Ghz), everything is fine and
> ffmpeg/Pthreads-w32 eagerly uses 97-99% of my CPU. But when I move the
> same code to a dual-core system (P4 3Ghz), it will never exceed exactly
> 50% of the CPU. By default it uses both cores at about 20/30. If I
> change the affinity and restrict it to one core, then it uses the whole
> thing but again won't exceed exactly 50% of the total CPU. I get the
> same results reading from and writing to a flash drive, so I don't think
> it's an I/O bottleneck.
>
> I'm posting this to the ffmpeg list as well, but it seems like this
> could be something related to Pthreads-w32. Does anyone have any
> thoughts about what might be going on?
>
> Thanks!
>
prev parent reply other threads:[~2007-11-12 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 20:33 Chris Stanley
2007-11-15 19:22 ` Chris Stanley [this message]
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=4738B89C.9020207@cctv.org \
--to=cstanley@cctv.org \
--cc=pthreads-win32@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).