![]() Any this will scale very well, not to mention the improved security because each task is isolated from the underlying OS. There is already a predefined ffmpeg image on github: docker run jrottenberg/ffmpeg \Ī single conversion will likely run slower because of the overhead but if you run mutliple instances concurrently this could be a huge benefit. And not just cpu but also memory and IOs.Įven more: Maybe you have different tasks that may run in the background and you don't care how long they take and you have tasks that should run fast, so you can put a weight on different tasks. Now you can limit how much resources a single ffmpeg instance may consume without even using ffmpeg commandline options. ![]() ![]() Let ffmpeg run with full horsepower (as denjello called it).FFMPEG is available for Mac OSX, Windows, Linux and many other platforms. FFMPEG is open source and free software licensed under the GNU General Public License. This may be a little old but this sounds like a perfect task for a container like docker. It supports an extensive number of formats including AVI, MPEG, MP4, WEBM and more. I can test it out.īut how do I change this setting? Everything I see online discusses this setting, but not the steps to change it. It's only used for conversions, so I've heard the best setting would be between 2 and 4. ![]() I've heard there's a -threads setting you can change, but I cannot find it. It seems ffmpeg tries to use all the resources available per conversion. I imagine when it opens, many people will be uploading at once. Issue during testing is that even only doing 4-5 at once, the server load skyrockets to an average of around 36. FFmpeg can be downloaded as an official version or through Linux packages, but it can also be compiled directly from the source code. I'm running videos through ffmpeg on a linux dedicated server to convert to mp4.
0 Comments
Leave a Reply. |