[FFmpeg-user] maximum CPU utilization with ffmpeg and libx264
Richard Buteau
rbuteau at rgbnetworks.com
Tue Mar 22 16:14:40 CET 2011
> -----Original Message-----
> From: ffmpeg-user-bounces at ffmpeg.org [mailto:ffmpeg-user-
> bounces at ffmpeg.org] On Behalf Of Reindl Harald
> Sent: Tuesday, March 22, 2011 2:54 AM
> To: ffmpeg-user at ffmpeg.org
> Subject: Re: [FFmpeg-user] maximum CPU utilization with ffmpeg and
> libx264
>
>
> Am 22.03.2011 02:41, schrieb George D Pylant III:
>
> > My understanding is that these cores support hyperthreading allowing
> > two threads to run simultaneously on each core.
>
> yes and no
> since it is not a full core / cpu you can not expect wonders HT is
> using on non-ht-cpus wasted parts of the die (to say it simple)
>
> > So why doesn't ffmpeg/libx264 use all "sixteen" cores, i.e. two
> > threads per core like handbrakecli does? -
>
> because you can not scale linear with more cpus and not every operation
> can benefit from multithreading
>
> who tells you that the 100% cpu from "handbrakecli" is not wasted for
> useless thread-synchronisation, try it and reduce the software to use
> only 8 threads, maybe it gets slightly faster than with 16
You actually get more throughput with X264 if you turn on hyperthreading I ran some benchmark with and without it about a year and half ago on Nehalem based systems. There was up to 15% more throughput with hyper-threading on and using all core (hyper threaded or not). I wasn't actually looking at system load but just the average fps. Maybe these tests should be run again just to make sure that is still true.
>
> --
>
> Mit besten Grüßen, Reindl Harald
> the lounge interactive design GmbH
> A-1060 Vienna, Hofmühlgasse 17
> CTO / software-development / cms-solutions
> p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
> icq: 154546673, http://www.thelounge.net/
More information about the ffmpeg-user
mailing list