Re: whats going on with the scheduler?
From: Andy Farkas (andyf_at_speednet.com.au)
Date: 07/08/03
- Previous message: Tinderbox: "[-CURRENT tinderbox] failure on sparc64/sparc64"
- In reply to: Terry Lambert: "Re: whats going on with the scheduler?"
- Next in thread: Dan Nelson: "Re: whats going on with the scheduler?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 8 Jul 2003 21:55:45 +1000 (EST) To: Terry Lambert <tlambert2@mindspring.com>
On Tue, 8 Jul 2003, Terry Lambert wrote:
> It's not clear what your link speed is, but it's possible that
> what's happening is that the setiathome processes are stalling
> waiting for work units because you are using up your available
> network bandwidth.
setiathome is a cpu intensive process. It touches the network maybe once
in a 24 hour period when it downloads a ~400k work unit which takes less
than 10 seconds over my 512k/128k dsl link and then proceeds to number
crunch. Stalling on work units is not whats happening.
> If this is what's ahppening, you might want to try bandwidth
> limiting the scp and/or running with Alt-Q and/or begging Julian
I *did* limit scp:
> scp -c blowfish -p -l 100 remote.host:filename .
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Tinderbox: "[-CURRENT tinderbox] failure on sparc64/sparc64"
- In reply to: Terry Lambert: "Re: whats going on with the scheduler?"
- Next in thread: Dan Nelson: "Re: whats going on with the scheduler?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]