<br><br>
<div class="gmail_quote">On Dec 10, 2007 9:44 AM, Wolfgang Grunewald <<a href="mailto:wmgrunewald@web.de">wmgrunewald@web.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">Chris Pinkham wrote:<br><br>> * On Sun Dec 09, 2007 at 11:34:02PM +0100, Wolfgang Grunewald wrote:<br>> > <a href="http://tinyurl.com/22xppv" target="_blank">http://tinyurl.com/22xppv</a><br>
><br>> There's some woman blocking the view in this graph.<br><br></div>Sorry for that! The MythTV graph shows constant disk activity<br>while the "cat while playing with mplayer" graph just shows<br>some high writing peaks every few seconds (besides that
<br>there's no activity at all).</blockquote>
<div> </div>
<div>There is more going on than just "cat with mplayer" in myth. Off the top of my head you have:</div>
<div> </div>
<div>1. MySQL database reads and writes for the seektable while recording</div>
<div>2. Any logging being done by the program</div>
<div>3. Reading and writing the actual recording</div>
<div>4. Any commercial flagging you have enabled</div>
<div> </div>
<div>All that adds up. Having run Myth for a while now, I *strongly* recommend separating your database and logs from your recording drive if you haven't done it already. It has made my system much more resiliant with regards to how many streams I can handle. Currently, on a lowly Athlon 2000, I can record 2 HD, 2 SD, watch any stream, and run two commflagging jobs all without disk issues.
</div>
<div> </div>
<div>Kevin</div></div>