<br><br><div class="gmail_quote">On 4 November 2010 16:03, Christopher Kerr <span dir="ltr"><<a href="mailto:mythtv@theseekerr.com">mythtv@theseekerr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thu, Nov 4, 2010 at 4:13 PM, Paul Buchanan <<a href="mailto:paul.buchanan@gmail.com">paul.buchanan@gmail.com</a>> wrote:<br>
> I'm using hardware that I've rescued from various sources to make one master<br>
> and one slave. 3ghz and 2.8ghz P4 CPUs.<br>
> Quite old I know ... so I'm trying to manage the load as best I can with<br>
> config tweaks.<br>
<br>
</div>Ah, fair enough - hot, power hungry, and pretty weak by todays<br>
standards. I have a P4 3.0GHz under my desk as a footrest - I suspect<br>
it has worked its last day ;o)<br>
<br>
I'd suggest you limit the system to 2 simultanous jobs and see how you<br>
go - real time commflagging isn't as CPU intensive as it might be,<br>
because it's capped at the framerate of the incoming video.<br>
<br>
Oh, and make sure you make life as easy as you can for it - put the<br>
database on a different disk to the recordings, and spread your<br>
recordings directories over 2+ disks too, if you can - made a huge<br>
difference to my (rather more powerful) system - with 3 harddrives, I<br>
can now record 6 programs (typically 5 SD and 1 HD, given how little<br>
real HD content we get here) with commflagging whilst playing a<br>
recording on a seperate frontend - I've never tried winding up both<br>
frontends at once on a Saturday night, but I suspect it'd handle it.<br>
<div><div></div><div class="h5"><br>
- Chris<br>
<br></div></div></blockquote><div><br>I'd even go as far as limiting the simultanous jobs to 1, especially if you ever export recordings, my P4 3.0GHz seems to run fine now I fixed my thermal throttling issues thanks to some suggestions from the list but I am using a nvidia GT240 to offload alot of the display processing to the GPU.<br>
<br>Cheers,<br><br>Anthony<br></div></div><br>