From owner-freebsd-current Thu Oct 12 10:17:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 8012F37B66C for ; Thu, 12 Oct 2000 10:17:44 -0700 (PDT) Received: from laptop.baldwin.cx (ether.osd.bsdi.com [204.216.28.196]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9CHGdi20940; Thu, 12 Oct 2000 10:16:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 12 Oct 2000 10:17:15 -0700 (PDT) From: John Baldwin To: Bob Bishop Subject: RE: -current grinds exceeding slow Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Oct-00 Bob Bishop wrote: > Hi, > > At 11:42 -0700 11/10/00, John Baldwin wrote: >>On 10-Oct-00 Bob Bishop wrote: >>> Hi, >>> >>> What's happened recently to make -current so slow? >>> [etc] >> >>I don't know. Can you try to narrow down the date by cvsupping or >>cvs updating with date tags to see when it started slowing down? > > More data: it's networking that's doing it, not NFS per se. I'm doing a > build with local sources on one of the affected boxes, on first impression > looks like that is up to speed. > > Both my affected boxes have ed NICs, I'll see if I can scare up a different > card to try in case it's the ed driver. Watch this space... It's not. My current box that is having problems has an fxp0 card. BTW, what speed is your processor? I'm curious because the PPro 200 I have here is having problems, but the PIII-700 isn't very affected. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message