Most of these suggestions were made on Slashdot on the "Redhat 8.0 Reviewed" topic (sorry, no link) - reworked:
Niceing (from highest to lowest priority)
*Renice esd/artsd to -15. If these don't get CPU right away when they need it, your sound will break up.
*Jack the nice value of X from 0 to -10. The nice value doesn't make it much "faster", but it does significantly improve latency. There is a debconf question for that, if you need to do it at all. Check first if it's not running nice -10 out of the box (my woody box did).
*gpm should be niced to match X when acting as a repeater. (Should it be even higher priority?)
*Software that's always sucking down a little CPU in the background but still should be interactive (like lopster or gtk-gnutella) should be niced to 5 or so.
*If you run any servers on your workstation, they should run around nice 10. They need to get back to the user, but they shouldn't make your UI get unpleasant when they get hit.
*Make all your cron jobs run at nice 20 (crontab -e, edit command line to contain nice -n20). They have no reason to demand interactive latency, and you do need said latency for your UI.
Low level tuning
*Turn on DMA and umasked interrupts (insert usual warnings about potential problems with really old computers having these on). Significantly reduces "jerkiness" in X when doing disk access, including paging. See the two following points (ZWiki seems not to be able to generate nested lists
). Try the options first, then run hdparm at boot time. The easiest way is to install DebianPackage:hwtools and edit /etc/init.d/hwtools .
*you can do "hdparm -c3 -d1 /dev/yourharddrivenamehere" with almost no risk
*with caution (backup your data first) you can play with the -u and -m options (preferentially with your device mounted ro)
Updating
*Use mozilla 1.1 (much faster redraw than 1.0)
*use an up-to-date version of gtk2 (wow, the version RH is packaging is much faster at rendering aa text than the old snapshot I had from Ximian)
*Use gnuserv mode in emacs/emacs
*use XFree86 4.2, it loads fonts a lot faster (because it uses a cache)
*develop directly from sid in order to get new packages that can make the system feel nicer. consider CopingWithUnstable though
Kernel
* compile your own kernel images that include things like the low-latency patch and the preemption patch which make the system feel faster. These are go to be included in the 2.6.x series and only require turning on before compiling. The low-latency patch is a special case where a prebuild kernel can be used for both desktop and server, by switching low-latency with "echo 1 > /proc/sys/kernel/low-latency".
其中有關於Niceing的問題
1.esd/artsd 這個要如何renice呢，還有我只是用oss這樣要如何renice
2.servers要如何renice，我說的是一開機就起來的那些server
最後 nice的效益會有差嗎
