[mythtv-users] Central Storage

Steven Adeff adeffs.mythtv at gmail.com
Fri Mar 6 18:31:30 UTC 2009

On Fri, Mar 6, 2009 at 1:07 PM, jedi <jedi at mishnet.org> wrote:
> On Fri, Mar 06, 2009 at 08:19:14AM -0800, Robert McNamara wrote:
>> >
>> > *5 family members with diverse tastes
>> > *15 upcoming free to air channels ( 5 of which are HD )
>> > *presently have at times have 3 VCRs and 3 Mythboxes recording simultaneously and some Mythboxes recording multiple streams.
>> >
>> Do you intend to record all 15 channels at once or something?  Even if
>> that were true...
>> Maximum Channel bandwidth:  19 Mbit/s
>> 5 family members watching at once at maximum bandwidth:  90 Mbit
>> 15 Channels at 19 Mbit: 281 Mbit
>> 371 Mbit Total, assuming everyone were watching at once and you were
>> recording all your channels at once (which would require at *least*
>> 7-8 tuner cards).
>> As steve mentioned, you will run into other I/O bandwidth long before
>> you saturate a gigE network.
>     When my multi-frontend/backend setup is going full bore, the
> "central storage server" seems to give out before the network does.
> 7 mythjobqueue jobs running with 4 recordings active seems to hammer
> the box pretty well. It's enough to leave the master backend with
> little (cpu/io) capacity left to service end users.
>     If you've got an extreme setup then perhaps you want to DEcentralize
> and keep activities as close to one particular box as possible. Perhaps
> have storage on each backend and do any processing there rather than
> pushing stuff accross the network.

don't let Myth run 7 job queue jobs.
I just upgraded my backend, but up until a week ago I had a lowly
Athlon64 3200+ as my backend with 5 HD capable tuners and a 6disc raid
5 array. I only let it run 2 job's and it worked pretty well.

Before you ask, read the FAQ!
then search the Wiki, and this list,
Mailinglist etiquette -

More information about the mythtv-users mailing list