From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 09:31:10 2003 Return-Path: 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 9272837B401 for ; Wed, 9 Jul 2003 09:31:10 -0700 (PDT) Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FAD043FA3 for ; Wed, 9 Jul 2003 09:31:09 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: by mailhub.yumyumyum.org (Postfix, from userid 1001) id C0B122A0; Wed, 9 Jul 2003 12:31:30 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mailhub.yumyumyum.org (Postfix) with ESMTP id B5BCD67 for ; Wed, 9 Jul 2003 12:31:30 -0400 (EDT) Date: Wed, 9 Jul 2003 12:31:30 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Message-ID: <20030709122610.E3831@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: wierd dsl performance with -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2003 16:31:10 -0000 Hi, Recently, for some wierd reason, with FreeBSD-CURRENT my DSL downloads have gotten about 10-15 KB/sec slower than they used to be.. I used to get 160KB/sec downloads, and now can only manage about 145. I was wondering if there are any ideas what is causing this. I'm sure it's a FreeBSD problem because when I boot up windows or hook my mac straight to the dsl modem, each of those gets the full 160KB/sec download (from the same site, ftp2.freebsd.org) but when I download from FreeBSD, the speed drops. I'm not sure if this happens in -STABLE, but it started happening sometime within the last month or 1.5 months. I tried checking out a cvs repository, then checking out FreeBSD-CURRENT from as early as 5/28/03 (uname -a shows 5.1-BETA), and I still see the problem. I'm going to try checking out one from mid-May and see if the problem still exists, but I was wondering if there is some kernel option or something similar that could be causing my problem. Thanks. Ken