Quote:
Originally Posted by bryrabknowles
This works in general but still limits to a single thread value.
During a full backup using multiprocess, some files are too small to multiprocess. If I have threads set at 1 because I use multiprocess=12, these smaller files take way longer to encode than they should because they're also stuck with a single thread.
|
Hi bryrabknowles,
in general everytime splitting is used an additional step with TSMUXER is needed to combine the single *.264 files into one. This takes time, too. I guess that's why jdobbs decided to define a minimum m2ts file size.
But which speed gain do you expect? Maybe you could post a log file so that we can see the time needed for encoding. I assume that we are talking about a few minutes only for the
whole rebuilding process. As a rule of thumb it was said already 30 years ago that speed gains below 33% are not noticable anyway. This applies to CPU, RAM and HDD Speed and for waiting
Even on my slower machine m2ts segments not being split (I use MULTIPROCESS=2) segments are encoded in 1-2 minutes.
So what are we talking about?
ggtop