[mythtv-users] Opinion on a P4 Backend // HDD Throughput

[Kevin Kuphal]

On Wed, Mar 5, 2008 at 4:25 PM, Gareth Glaccum <
gareth.glaccum at btopenworld.com> wrote:

>
> ----- Original Message -----
> From: <greg at nodecam.com>
> >On my system (one firewire tuner, one PVR 250) I could cause problems by
> >recording HD, playing back the same HD stream on a delay and recording SD
> >at the same time.  As soon as I put in a new disk and separated
> recordings
> >from database/logging, the problems went away.
>
> That doesn't really make sense. Logging and database access is a minimum
> in
> the situation you desribed (EIT scanning is about it I think), just moving
> the logs and database should have made little difference really.
> Ok, if you are running more than just myth, a lot of logging and seperate
> database accesses in the background then this would make a difference.


Myth writes *alot* of data for the seektables when recording.  The commflag
process reads that as well as your playback so when you start to get a
handful of recordings, especially HD where the bitrates are higher, the
database gets hit pretty hard.

Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080305/e84e6f13/attachment.htm