it absolutely pegs the CPU usage at a full 100% on all cores
rpm -Uhv http://www.vacuumtube.org.uk/folding/fedora/11/x86_64/folding-release-1-2.noarch.rpm
yum --enablerepo=folding-testing update kernel\*
yum install schedtool
schedtool -D -e ./fah6 ........
schedtool -B -n 19 -e ./fah6 .......
ThunderRd wrote:SCHED_IDLEPRIO didn't work for me as advertised in the FAQ, in fact it used less CPU than running without schedtool.
ThunderRd wrote:I wrote to Con about this and he has said it appears to be a bug and will address it later after larger fish are fried. In the meantime, running the client without schedtool has been fine for me, 99-100% constantly, and the desktop doesn't seem to suffer at all, afaict.
ThunderRd wrote:I'm stunned that this topic hasn't generated much interest.
Galahad wrote:I'd be happy to know how to apply this patch. In steps please.
patch < 2.6.30-sched-bfs-208.patch -p1
cp /boot/config-$(uname -r) .config && yes "" | make oldconfig
tear wrote:It's possible bfs improves behavior (vs. stock) when CPU/mem affinities are unset but that is really N/A to me.
Configure your kernel with 1000Hz, preempt ON and disable dynamic ticks.
You shouldn't need to tune BFS virtually ever. The only tunable for the
scheduler itself is the rr_interval value (see documentation). Try 3ms if
latency is everything to you. When compiling software, do not use more jobs
than you have CPUs! So make -j2 on dual core, -j4 on quad core and so on.
Nice levels are strictly obeyed so if you nice your compiles they'll be
virtually unnoticeable. (nice -n 19 make -j2). Run your distributed computing
clients SCHED_IDLEPRIO (eg folding at home, mprime etc):
schedtool -D -e mprime
Run your audio and video apps SCHED_ISO:
schedtool -I -e amarok
JackOfAll wrote:tear wrote:It's possible bfs improves behavior (vs. stock) when CPU/mem affinities are unset but that is really N/A to me.
Would you mind elaborating on exactly what you're doing with regard to CPU/mem affinities? (Using numactl and then locking the 15 fah cores individually to CPU cores, or just starting launching the fah6 with taskset -c ....... ????) Hope you don't mind. I'm curious as I'm currently building a new rig with a pair of W5580's that will run the bigadv.
[fah@octopus cpuset]$ pwd
[fah@octopus cpuset]$ find all0 -maxdepth 1 -mindepth 1 -type d
[fah@octopus cpuset]$ cat all0/cpus
[fah@octopus cpuset]$ cat all0/mems
[fah@octopus cpuset]$ cat all0/node-0/cpus
[fah@octopus cpuset]$ cat all0/node-0/mems
[fah@octopus cpuset]$ cat all0/node-1/cpus
[fah@octopus cpuset]$ cat all0/node-1/mems
Users browsing this forum: Google [Bot] and 1 guest