![]() When using distributed encoding all of my servers seem to be encoding except my main machine/client (newer HP). With that said, I also have another HP desktop, HP laptop, and ASUS laptop and if memory serves, all are Intel Core i5's with 8GB of RAM for each. I LOVE Ripbot264 and can completely use it on my main machine (Desktop - HP AMD Ryzen 7, 16GB RAM) with no issues. Good morning, I'm going to apologize up front because I know enough to be dangerous but that's about it. GPUs do a much better job for the dollar cost if your requirements are getting single videos out the door quickly. With all of that said, the cost effectiveness today of CPU transcoding is pretty low. But if you're clever, maybe chopping longer videos into chunks, transcoding in parallel and then gluing them together (although that in itself can be a bit tricky). Not useful if you don't have a lot of transcodes to run in parallel of course (we had *thousands* of transcodes to do in parallel for big customers like the ABC and others). We found running transcode jobs on the farm most efficient when we capped ffmpeg to 16 threads and then ran multiple concurrent jobs. Where I worked previously they had a render farm - somewhere in the order of 100+ machines running 54 - 72 cores (dual socket Xeons) per machine, with 256-512GB RAM per machine. There's not much you can do there, as there's certain parts of the quantisation pipeline that just don't scale well past a certain level due to how the maths works. Click to expand.ffmpeg (the library behind Handbrake) scaling works up to about 16 cores well, then tapers off after that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |