I'm interested in finding out if multiple user experience consistently corresponds with the reported encoding benchmarks for some of the Ryzen 9's of 40-50 fps? I had a threadripper some years back with lots of cores but did not utilise them all and encoded at around 10-15 fps.
If you are currently encoding at 40+ fps, then I'd like to know what your setup is.
Thanks
Benchmarks
-
Carsten
- Posts: 2947
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Benchmarks
I remember that DCP-o-matic had issues at first with some of the earlier Threadrippers. Experiences with the Ryzen 5/7/9 seem to be solid, also there have been a number of code optimisations that increased encoding speed considerably. I don't think a system needs to be specifically optimised to benefit, but of course, a fast internal M.2 SSD and enough RAM is a prerequisite when using many threads and high encoding fps. Enough RAM means 16GB for 2k and probably 32GB for 4k. But that should be standard for that kind of system nowadays. Note that the official benchmarks are all 2k.
Look at this list: https://www.cpubenchmark.net/multithread/
Looks as if currently the Ryzen 9 9950X3D gives you the best price/performance ratio. However, I read about some stability issues with them, so, maybe better to buy a bit more conservative, since full speed encoding will really heat up the CPU for a considerable time.
One hint - when encoding at 40+ fps, the final hash calculation actually becomes sort of a bottleneck, as it is single-threaded based on media assets. You can force it to multi-threaded when creating the DCP with multiple reels - then each reel/asset will be hash checked through it's own thread. You definitely need to create the DCP on an internal SSD in that case, since it's also I/O intensive.
Look at this list: https://www.cpubenchmark.net/multithread/
Looks as if currently the Ryzen 9 9950X3D gives you the best price/performance ratio. However, I read about some stability issues with them, so, maybe better to buy a bit more conservative, since full speed encoding will really heat up the CPU for a considerable time.
One hint - when encoding at 40+ fps, the final hash calculation actually becomes sort of a bottleneck, as it is single-threaded based on media assets. You can force it to multi-threaded when creating the DCP with multiple reels - then each reel/asset will be hash checked through it's own thread. You definitely need to create the DCP on an internal SSD in that case, since it's also I/O intensive.
-
IoannisSyrogiannis
- Posts: 277
- Joined: Mon Nov 13, 2017 8:40 pm
Re: Benchmarks
I wonder if the objective here is high encoding framerate or high CPU power. If it's about the CPU power, then Carsten has covered you. Yet, if it is encoding framerate, maybe you would want to go for GPU utilization.
A copy of such a proprietary software and a corresponding GPU might give you a higher FpS/cost ratio.
If your target is above those rates, there are IP cores that could go much higher. You can look into intoPIX configurations for FPGA & ASIC, for instance.
Focusing on CPU, when your objective is (DCP JPEG2000) encoding might not be the way to go.
A copy of such a proprietary software and a corresponding GPU might give you a higher FpS/cost ratio.
If your target is above those rates, there are IP cores that could go much higher. You can look into intoPIX configurations for FPGA & ASIC, for instance.
Focusing on CPU, when your objective is (DCP JPEG2000) encoding might not be the way to go.