On Sun, Oct 13, 2019 at 02:10:02PM +0100, Kieran Kunhya wrote:
> >
> > Michael, I have updated the patch to limit thread_count to [1,1,
> > avctx->height/4],
> > why height/4, it's borrowed from dxv.c, please give comments whether it's
> > proper.
> >
>
> For the lack of big speed improvement,
>
> Michael, I have updated the patch to limit thread_count to [1,1,
> avctx->height/4],
> why height/4, it's borrowed from dxv.c, please give comments whether it's
> proper.
>
For the lack of big speed improvement, make sure you are giving each thread
a slice in order.
Kieran
On Fri, Oct 11, 2019 at 09:05:27PM +0200, Michael Niedermayer wrote:
> On Sun, Sep 22, 2019 at 11:55:49AM +0800, lance.lmw...@gmail.com wrote:
> > From: Limin Wang
> >
> > The multithread is avoid one core cpu is full with other filter like scale
> > etc.
> > About the performance, the gain is
On Sun, Sep 22, 2019 at 11:55:49AM +0800, lance.lmw...@gmail.com wrote:
> From: Limin Wang
>
> The multithread is avoid one core cpu is full with other filter like scale
> etc.
> About the performance, the gain is very small, below is my testing for
> performance.
> In order to avoid the disk
Michael, have updated the patch by your suggestion, please help to review the
final version.
On Sun, Sep 22, 2019 at 11:55:49AM +0800, lance.lmw...@gmail.com wrote:
> From: Limin Wang
>
> The multithread is avoid one core cpu is full with other filter like scale
> etc.
> About the
From: Limin Wang
The multithread is avoid one core cpu is full with other filter like scale etc.
About the performance, the gain is very small, below is my testing for
performance.
In order to avoid the disk bottleneck, I'll use stream_loop mode for 10 frame
only.
./ffmpeg -y -i
