<div class="gmail_quote">On Thu, Jan 12, 2012 at 20:12, criggie <span dir="ltr"><<a href="mailto:criggie@criggie.org.nz">criggie@criggie.org.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 12/01/12 18:54, Steve Hodge wrote:<br>
> If you're going to be recording a lot of stuff<br>
> simultaneously then perhaps having MySQL on a separate drive might be<br>
</div>> important...<br>
<br>
Why? The mysql output is a single record to the recordings table, a<br>
single record in the recorded table, and maybe a few state updates that<br>
the tuner is in use.<br></blockquote><div><br>I think it builds the index in recordedseek during recording as well. That table is current 3.5M rows in my db, seems to be about 2 rows a second added per recording. So on balance it really shouldn't be an issue, it's just something I've seen people raise as a concern in the past.<br>
<br>Cheers,<br>Steve<br><br></div></div>