[x264-devel] how to get optimal thread number

[applemax82 at 163.com]

Hi,

Thanks for your reply. I think it will take much effort to know multi-thread structure in x264 encoder, and then decide how to use threads and set some related parameters.

B.R.

Andrew

 
From: Alex Cohn
Date: 2015-11-08 20:27
To: Mailing list for x264 developers
Subject: Re: [x264-devel] how to get optimal thread number
X264_THREADS_AUTO setting is only good if video encoding is the only
important thing your device does. There may be other activity going on
in your CPU. For example, video chat applications must reserve some
resources for the down-channel, decoding the video stream, displaying
everything, and also dealing with audio. In our case, these
considerations resulted in dedicating 2 threads to x264 and only one
for the decoder.
 
But your mileage may vary.
 
Cheers,
Alex
 
On Sun, Nov 8, 2015 at 9:49 AM, Simon Horlick <simonhorlick at gmail.com> wrote:
> Internally, x264 selects 1.5*cores (with some extra logic to cap the number
> and fewer for sliced threads). If you aren’t sure what to use, set this to
> X264_THREADS_AUTO.
>
> Thanks,
>
> Simon
>
> On 8 Nov 2015, at 15:43, applemax82 at 163.com wrote:
>
> Hi,
>
> I have one question about setting optimal thread number in x264 encoder.
> There are many factors affecting encoder performance, such as cpu, input
> parameter, and concurrent tasks.
>
> Is there some recommendation about selecting optimal thread number in x264
> encoder in some situation?
>
> Thanks
>
>
> Andrew
>
>
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel
>
>
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel
>
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
https://mailman.videolan.org/listinfo/x264-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20151108/5f533f0f/attachment.html>