From: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH V2] lavc/libvpx: increase thread limit to 64 Date: Thu, 6 Oct 2022 16:03:27 +0200 Message-ID: <CADXbNkRnZCZrkk72ZR9L7pF=Opc290pd=ucDTD2UsENnhJPb=g@mail.gmail.com> (raw) In-Reply-To: <20221006134959.771-1-ovchinnikov.dmitrii@gmail.com> Removed unnecessary comment as requested by Ronald S. Bultje. some more thoughts about the patch: This is my deduction from what I could find - There was a hard limit of 16 threads in libvpx as there was no benefit to adding more threads based upon the parallelism available in the the codec. This was based upon resolutions upto 3840x2160 (more details below). For 4k/8K videos this restriction does not allow enough parallelism to be exploited. Adding more threads improves performance for higher resolution videos. Details: Tiling and Threading Recommendations Tiling splits the video frame into multiple columns, which slightly reduces quality but speeds up encoding performance. Tiles must be at least 256 pixels wide, so there is a limit to how many tiles can be used. Depending upon the number of tiles and the resolution of the output frame, more CPU threads may be useful. There is limited value to multiple threads when the output frame size is very small. The following settings are recommended for tiling and threading at various resolutions. The number of threads is doubled as there is an option row-mt when set allows row-based multithreading within the tiles. Frame Size | Number of tile-columns | Number of threads 320x240 | 1 (-tile-columns 0) | 2 640x360 | 2 (-tile-columns 1) | 4 640x480 | 2 (-tile-columns 1) | 4 1280x720 | 4 (-tile-columns 2) | 8 1920x1080 | 4 (-tile-columns 2) | 8 2560x1440 | 8 (-tile-columns 3) | 16 3840x2160 | 8 (-tile-columns 3) | 16 In ffmpeg, the number of tiles is controlled with the -tile-columns parameter and the number of threads by -threads. For example, a 640x480 encode would use the command-line -tile-columns 2 -threads 4. _______________________________________________ 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:[~2022-10-06 14:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-06 13:49 OvchinnikovDmitrii 2022-10-06 14:03 ` Dmitrii Ovchinnikov [this message] 2022-10-06 14:12 ` Andreas Rheinhardt 2022-10-25 15:55 ` Dmitrii Ovchinnikov 2022-11-21 17:34 ` James Zern 2022-11-23 14:25 ` Dmitrii Ovchinnikov
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='CADXbNkRnZCZrkk72ZR9L7pF=Opc290pd=ucDTD2UsENnhJPb=g@mail.gmail.com' \ --to=ovchinnikov.dmitrii@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