Date: Wed, 20 Jun 2007 15:52:41 -0400 (EDT) From: David Cross <dcross@okcupid.com> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: Re: Very slow sed... Message-ID: <20070620155139.P48331@max.okcupid.com> In-Reply-To: <20070620192003.GA72641@eos.sc1.parodius.com> References: <20070620100737.S56928@max.okcupid.com> <20070620192003.GA72641@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 | >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070620155139.P48331>