[mythtv] [mythtv-commits] Ticket #1791: Stop transcode/commflag from hogging the CPU while recording/playback is in progress.

[Daniel Staaf]

f-myth-users at media.mit.edu wrote:
> (At some point, I"ll probably try out Dapper, which has a newer kernel, 
> and either 0.18.1 there as a base case [to test CFQ and ionice] or 0.20
> directly in the hope that 20's scheduler query hits mysql less hard.

Upgrading to Dapper would seem to be a good choice, the Dapper kernel
(2.6.15 but almost 2.6.16) has quite a few performance fixes compared to
2.6.12 and mysql version 5.0.22 + fixes may work better than 4.0.24 in
Breezy too.

> But until then, it'd be nice if I could figure out if Breezy/0.18.1
> can be made to work.)

Stuart mentioned the deadline scheduler (essentially what linux 2.4.x
uses) but I think not.

> It'll be a -long- time before I'm running 2.6.18, since even Dapper
> doesn't run it, and I'd like to stay with out-of-the-box kernels
> unless it's my only alternative.

But you are running beta-quality out-of-tree drivers with known DMA
problems [1] so compiling your own kernel may not be such a bad idea
after all.

I would suggest that you at least try booting a self-compiled Linux
2.6.17.13 [2] + ivtv-0.7.0 [3] and see if that makes any difference.

/ Daniel

[1] http://www.gossamer-threads.com/lists/ivtv/devel/31647
    http://www.gossamer-threads.com/lists/ivtv/devel/31936

[2] http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.17.13.tar.bz2

[3] http://dl.ivtvdriver.org/ivtv/archive/0.7.x/ivtv-0.7.0.tar.gz
    http://ivtvdriver.org/index.php/Firmware