From owner-freebsd-current@FreeBSD.ORG  Tue Jul  8 04:55:50 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 841DB37B401; Tue,  8 Jul 2003 04:55:50 -0700 (PDT)
Received: from franky.speednet.com.au (franky.speednet.com.au [203.57.65.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 24DDB43FA3; Tue,  8 Jul 2003 04:55:49 -0700 (PDT)
	(envelope-from andyf@speednet.com.au)
Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au
	[203.38.96.242])h68Btksw017277;	Tue, 8 Jul 2003 21:55:47 +1000 (EST)
	(envelope-from andyf@speednet.com.au)
Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au
	[203.38.96.242])h68Btj2b008966;	Tue, 8 Jul 2003 21:55:46 +1000 (EST)
	(envelope-from andyf@speednet.com.au)
Date: Tue, 8 Jul 2003 21:55:45 +1000 (EST)
From: Andy Farkas <andyf@speednet.com.au>
X-X-Sender: andyf@hewey.af.speednet.com.au
To: Terry Lambert <tlambert2@mindspring.com>
In-Reply-To: <3F0AA2DE.13035C1@mindspring.com>
Message-ID: <20030708214151.R8850-100000@hewey.af.speednet.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: freebsd-smp@freebsd.org
Subject: Re: whats going on with the scheduler?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jul 2003 11:55:50 -0000

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/