To verify if CPU scheduling is your problem you could try "cpuburn". Commands in this package are: burnP6, burnK7, ect. (optimized for different CPU types) and they just waste CPU cycles. Run your test-app with higher prio together with burnXY:
$ burnP6 &
$ sudo nice -1 wine CoD4
If your test app shows much more or less(!) jitter than when running alone, then there is a problem with CPU scheduling and/or power-saving on your system. If it does not make a big difference, then it is more likely a problem with the video driver, DMA transfers or similar.
About me: I am not a Linux kernel guru. Me too, I just saw these CPU scaling issues since Hardy. Here they were gone since Jaunty final. But I am glad to help finding the cause or solutions for systems which are still affected.
To verify if CPU scheduling is your problem you could try "cpuburn". Commands in this package are: burnP6, burnK7, ect. (optimized for different CPU types) and they just waste CPU cycles. Run your test-app with higher prio together with burnXY:
$ burnP6 &
$ sudo nice -1 wine CoD4
If your test app shows much more or less(!) jitter than when running alone, then there is a problem with CPU scheduling and/or power-saving on your system. If it does not make a big difference, then it is more likely a problem with the video driver, DMA transfers or similar.
About me: I am not a Linux kernel guru. Me too, I just saw these CPU scaling issues since Hardy. Here they were gone since Jaunty final. But I am glad to help finding the cause or solutions for systems which are still affected.