[RC5] If you were writing our next client...

Martin Schroeder list-dist-rc5 at dream.kn-bremen.de
Sun May 9 00:30:06 EDT 1999


In <Pine.LNX.3.91.990502122703.12318A-100000 at lynn.ci-n.com> John Campbell <jcampbel at lynn.ci-n.com> writes:
>	I have a 386DX-40 that I test new Linux kernels on before upgrading
>my more important machines. This means that it compiles a lot of kernels.
>Because it's so slow, I've experimented quite a bit to see how to minimize
>the time it takes. One of the things I've tried was shutting the client down
>before I started the compile. With the client shut off, it takes the machine
>between 3:45 and 4 hours to build a 2.2 kernel. With the client running, it
>takes it between 4 hours and 4:15. So the client, on average, is getting 15
>minutes of CPU time over a four hour compile. That's nothing like a 50/50
>split, more like 90/10. 

Use loadwatch. It will stop the client (or any program given as its parameter)
when the load reaches a given watermark and restart the client when the load
goes unter another watermark. Ask freshmeat.net on how to get it.

Best regards
	Martin

-- 
             Martin Schr"oder, martin.schroeder at acm.org
Live your life as an exclamation, not an explanation.

--
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest



More information about the rc5 mailing list