On 05/01/2012 04:59 AM, Brian K. White wrote:
The only thing you can do yourself immediately without making hairy changes to your system or becoming a developer or tester is you can try running the rsync with a lower i/o priority using "ionice". It will still flush the disk cache with rsync data that will still slow down all other disk access, but ionice should at least make it so that the kde proccesses get higher scheduling priority than the rsync process, so when kde tries to load some library or config file or data file, it still has to do it the slow hard way from the real disk, but it jumps to the front of the line and does it now instead of waiting for rsync to finish.
I don't think it's a cpu priority problem, so look at "ionice" not regular "nice"
Ok, here is an example - is this the right syntax? When I open up Bash, before running the rsync command, I will type the following: $ ionice -c 2 -n 7 rsync This will set the class to 2 for "best effort" and the scheduling data to 7 for lowest priority. After that, I can just run rsync? My script has several lines of rsync in it. Do I need to have the ionice before each one? Or is one time sufficient? Thanks again -- George Olson, still learning openSUSE and loving it Box #1: 12.1 | KDE 4.8.2 | AMD Athlon X3 | 64 | nVidia 8500GT | 4GB RAM Box #2 12.1 | KDE 4.7.2 | Pentium 4 (2core) | 32 | Intel 82915G | 2GB RAM Lap #1: 12.1 | KDE 4.8.2 | Core2 Duo T8100 | 64 | Intel 965GM | 3GB RAM Lap #2: 12.1 | KDE 4.8.2 | Core Duo T2400 | 32 | NVIDIA Quadro NVS 120 | 2GB RAM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org