[mythtv-users] How MANY backend threads!?!?!?

Mike Perkins mikep at randomtraveller.org.uk
Thu Oct 14 22:12:21 UTC 2010


Steve Smith wrote:
>
> I think this is a symptom of the BE getting too monolithic. A more
> modular approach would enable more flexibility without having to be
> always playing catchup.
> 
It might be useful if the spawned parts of mythbackend actually had different 
names so one could figure out what was happening. 32 threads of 'mythbackend' 
isn't really meaningful, whereas if some of them were, I dunno, 'mythgenpreview' 
for example, one could see what was what.

We already have 'mythtranscode', 'mytharchive',... so why not extend this scheme 
to forked processes? I understand it might not be so easy with threads, but still...

There are a number of unix examples of programs which are the same binary but 
behave differently according to what name they are called with.

-- 

Mike Perkins



More information about the mythtv-users mailing list