RE: experiences using "options SCHED_ULE"

Indeed, my daily buildworld routine usually takes somewhere around 2 hours. 
Today it was closer to 3 hours. I experience reduced interactivity. The 
pointer (choppily) follows the mouse instead of moving with it. Many times 
when this is happening, I can look at top and see that two processes (one 
for each processor) are taking over 90% of the processor time each. These 
processes are Standford's Folding_at_Home client which has nice = 20. Certainly 
processes with nice = 20 shouldn't keep my mouse from moving smoothly. At 
first I thought this was only when the system hadn't been used interactively 
for a while, but since then I've noticed that it happens whenever it feels 
like it. I tried using idprio on the processes, but that requires root 
(which I have but shouldn't be forced to use for this), and I experienced a 
system freeze shortly thereafter (the first system freeze since the last 
time I tried the nvidia-driver).
I hope there's something helpful in here,
--
Evan Dower
Undergraduate, Computer Science
University of Washington
Public key: http://students.washington.edu/evantd/pgp-pub-key.txt
Key fingerprint = D321 FA24 4BDA F82D 53A9  5B27 7D15 5A4F 033F 887D




>From: rosi <rosi_at_encephalon.de>
>To: freebsd-current_at_freebsd.org
>Subject: experiences using "options SCHED_ULE"
>Date: Fri, 13 Feb 2004 08:59:21 +0100
>
>hello,
>
>i know ...
>
>[/usr/srs/sys/conf/NOTES...]
># SCHED_ULE is a new experimental scheduler that has been designed for SMP, 
>but will work just fine on UP too.  Users of this scheduler should expect 
>some hicups and be prepaired to provide feedback.
>[...]
>
>... so here is the feedback.
>
>We using FreeBSD 5.2.1 p2 on SMP machines (i386 / Dual-P3 / Dual-Xeon).
>These servers running Apache+Suexec+PHP+Perl+Python and nfs(4).
>
>We were curiously in the new scheduler and so we test it.
>
>After building and installing the kernel (the only! thing that changed was 
>"options SCHED_ULE") we see the system takes much more cpu time.
>
>                            CPU time in %
>			usr	sys	idl
>options SCHED_ULE      	20-25	60-75	0-20
>options SCHED_4BSD	30-35	35-40	0-35
>
>
>Also we "see" much more suexec and php processes (usually, you can't see 
>them because they are processed to fast ;) ) and the whole system felt 
>slowly.
>
>On the search for the reason why the machine takes so much cpu time for 
>system, we found 400% to 500% more interrupts on the NIC's(fxp/em).
>
>After building and installing a new kernel using SCHED_4BSD, the whole 
>system runs like always. Very fast and well.
>
>If it is necessary, i would post more informations.
>But i think the "problem" is reproducibly on i386 SMP machines.
>
>Naturally we will also test the SCHED_ULE again, if something changed.
>
>---
>Frank
>rosi_at_encephalon.de
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"

_________________________________________________________________
Create your own personal Web page with the info you use most, at My MSN. 
http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/