From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 20 19:52:45 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E174A16A400 for ; Wed, 20 Jun 2007 19:52:45 +0000 (UTC) (envelope-from dcross@okcupid.com) Received: from mail0.okcupid.com (mail0.okcupid.com [66.59.66.16]) by mx1.freebsd.org (Postfix) with ESMTP id A5F0413C4AE for ; Wed, 20 Jun 2007 19:52:45 +0000 (UTC) (envelope-from dcross@okcupid.com) Received: from max.okcupid.com (max.okcupid.com [216.254.112.36]) by mail0.okcupid.com (8.13.4/8.13.4) with ESMTP id l5KJr6Vq039701; Wed, 20 Jun 2007 15:53:07 -0400 (EDT) (envelope-from dcross@okcupid.com) Received: from max.okcupid.com (localhost [127.0.0.1]) by max.okcupid.com (8.13.6/8.13.6) with ESMTP id l5KJqfLr048428; Wed, 20 Jun 2007 15:52:41 -0400 (EDT) (envelope-from dcross@max.okcupid.com) X-DomainKeys: Sendmail DomainKeys Filter v0.3.3 max.okcupid.com l5KJqfLr048428 Received: from localhost (dcross@localhost) by max.okcupid.com (8.13.6/8.13.6/Submit) with ESMTP id l5KJqfZk048421; Wed, 20 Jun 2007 15:52:41 -0400 (EDT) (envelope-from dcross@max.okcupid.com) Date: Wed, 20 Jun 2007 15:52:41 -0400 (EDT) From: David Cross To: Jeremy Chadwick In-Reply-To: <20070620192003.GA72641@eos.sc1.parodius.com> Message-ID: <20070620155139.P48331@max.okcupid.com> References: <20070620100737.S56928@max.okcupid.com> <20070620192003.GA72641@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Wed, 20 Jun 2007 20:04:14 +0000 Cc: freebsd-hackers@FreeBSD.org Subject: Re: Very slow sed... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 19:52:46 -0000 Thanks all.. it was the memory. It wasn't "bad".. .memtest (or anythign else didn't actually fail, the only way I could tell is with a stopwatch and watching loop times)... but pulling 1/2 of the RAM fixed it.. it doesn't matter which set was in, as long as both sets its fine. -- David E. Cross On Wed, 20 Jun 2007, Jeremy Chadwick wrote: > On Wed, Jun 20, 2007 at 10:24:01AM -0400, David Cross wrote: >> Ok the subject line is misleading.. but I don't know how else to put it. I >> have a machine on which SOME programs are slow. VERY SLOW. Other programs >> run just fine. I cannot seem to find the source of the problem. > > Two things I can think of: > > 1) Memory issues -- memtest86 could help show this kind of problem. Try > removing memory, and if the problem continues, swapping the pair you > removed with the pair that's installed. > > 2) Disk issues -- reading /usr/bin/sed off the disk where there's a > soon-to-be-bad block. The disk may be trying to work around it and > doing a delayed read (inducing EC). This seems less likely to be the > case than bad memory, but I've seen it happen. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | >