From: "mypopy@gmail.com" <mypopy@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3] lavc/libvpx: remove thread limit Date: Tue, 10 Jan 2023 18:47:05 +0800 Message-ID: <CACYjbn2VxYNY+zuz22y5sAY4_nrpEr+fRVmHeV=qyt+QnDndrw@mail.gmail.com> (raw) In-Reply-To: <20230105104151.2055-1-Dmitriy.Ovchinnikov@amd.com> On Thu, Jan 5, 2023 at 6:42 PM Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com> wrote: > > From: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com> > > This change improves the performance and multicore > scalability of the vp9 codec for streaming single-pass encoded videos. The > current thread limit for ffmpeg codecs is 16 (MAX_AUTO_THREADS in > pthread_internal.h) due to a limitation in H.264 codec that prevents more > than 16 threads being used. > > Increasing the thread limit to 64 for vp9 improves > the performance for encoding 4K raw videos for streaming by up to 47% > compared to 16 threads, and from 20-30% for 32 threads, with the same quality > as measured by the VMAF score. > > Did not need to add a check for limit in libvpx as it is already present > in libvpx/vp9/vp9_cx_iface.c: > RANGE_CHECK_HI(cfg, g_threads, 64); > As demonstrated by following message when -threads is set to anything more than 64 > [libvpx-vp9 @ 0x30ed380] Additional information: g_threads out of range [..64] > > --- > libavcodec/libvpxdec.c | 2 +- > libavcodec/libvpxenc.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/libvpxdec.c b/libavcodec/libvpxdec.c > index 9cd2c56caf..19407092d0 100644 > --- a/libavcodec/libvpxdec.c > +++ b/libavcodec/libvpxdec.c > @@ -88,7 +88,7 @@ static av_cold int vpx_init(AVCodecContext *avctx, > const struct vpx_codec_iface *iface) > { > struct vpx_codec_dec_cfg deccfg = { > - .threads = FFMIN(avctx->thread_count ? avctx->thread_count : av_cpu_count(), 16) > + .threads = avctx->thread_count ? avctx->thread_count : av_cpu_count() > }; > > av_log(avctx, AV_LOG_INFO, "%s\n", vpx_codec_version_str()); > diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c > index 9aa5510c28..0627e13973 100644 > --- a/libavcodec/libvpxenc.c > +++ b/libavcodec/libvpxenc.c > @@ -942,7 +942,7 @@ static av_cold int vpx_init(AVCodecContext *avctx, > enccfg.g_timebase.num = avctx->time_base.num; > enccfg.g_timebase.den = avctx->time_base.den; > enccfg.g_threads = > - FFMIN(avctx->thread_count ? avctx->thread_count : av_cpu_count(), 16); > + avctx->thread_count ? avctx->thread_count : av_cpu_count(); > enccfg.g_lag_in_frames= ctx->lag_in_frames; > Do you check the change with the old version libvpx? as I know, older versions libvpx setting the number of threads higher than 16 will cause a crash, so I think at least a version check needs to be added > if (avctx->flags & AV_CODEC_FLAG_PASS1) > -- > 2.38.1.windows.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-01-10 10:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-05 10:41 Dmitrii Ovchinnikov 2023-01-05 17:14 ` Tomas Härdin 2023-01-10 3:06 ` James Zern 2023-01-10 10:47 ` mypopy [this message] 2023-01-11 1:23 ` James Zern 2023-01-17 22:06 ` James Zern
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='CACYjbn2VxYNY+zuz22y5sAY4_nrpEr+fRVmHeV=qyt+QnDndrw@mail.gmail.com' \ --to=mypopy@gmail.com \ --cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git