I don't see any obvious settings to limit the number of concurrent post-processing tasks, but there is a way to 'throttle' them, which might help reduce the aggregate load on the server and give you back enough headroom for LINK clients:
http://snapstream.helpserve.com/inde...d=1416&nav=0,1
I concur that some level of control here would be useful: let me decide how much horsepower gets used on post-processing tasks, and when.
In increasing order of preference, here's my wishlist for such a feature:
1) setting that limits the number of post-processing jobs, regardless of the number of detected cores
2) setting that limits the number of post-processing jobs based on available CPU capacity:
% CPU idle > 75, run N jobs
% CPU idle > 50 < 75, run 1 job
% CPU idle < 50, run 0 jobs
3) setting to limit the number of post-processing jobs based on a set of criteria:
- number of connected LINK machines
- number of actively recording tuners
- CPU loadings, as described in 2)
- number of cores, as described in 1)
- different parameters for different post-processing windows ("Immediately" vs "After-Hours")
While this may seem overly complex, it doesn't take long to imagine a scenario where you might care about the logic used to govern such things:
For example, say the BTV server has recorded five shows during a given evening, and is both recording a sixth and chewing on two post-processing jobs when I sit down and fire up playback from one of my LINKs. Ideally, I'd like BTV to recognize that a LINK has connected, immediately put all post-processing (PP from here on, geez I need a macro) on hold *except* perhaps the jobs related to the show I'm watching (gotta have those SmartSkip markers), then continue the on-hold PP jobs sometime after I've stopped viewing a program via LINK, or simply defer them until the After-Hours window.
But if we can't get that level of control, I guess I could be happy with trickle-feeding them through a single core, just like tscales wants.
