From owner-freebsd-current Fri Jan 24 14:12:59 2003 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 5F5BD37B401 for ; Fri, 24 Jan 2003 14:12:58 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E5A843F18 for ; Fri, 24 Jan 2003 14:12:54 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 76047 invoked by uid 1000); 24 Jan 2003 22:12:55 -0000 Date: Fri, 24 Jan 2003 14:12:55 -0800 (PST) From: Nate Lawson To: Terry Lambert Cc: freebsd-current@freebsd.org Subject: Re: Performance problems with 5.0-RELEASE In-Reply-To: <3E31B72F.9349FD17@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 24 Jan 2003, Terry Lambert wrote: > Nate Lawson wrote: > > > > Every time machine is under heavy load (CPU, network, disks) it > > > > completely jamms for fraction of a second for every ten seconds or so, > > > > everything just stops and then continues. I noticed this while compiling > > > > software and copying files over NFS while listening to MP3's, later > > > > realized it wasn't just MP3's that lagged, but the whole machine, > > > > including console and everything. > > > > > > If you lean on the keyboard, or if you set up the network adapters > > > as "entropy" sources, does the problem fix itself? > > > > This can't be it since /dev/random is non-blocking in 5.x > > See other posting; though I could certainly write an app that > would keep hitting /dev/random until it got what it wanted... In fact, it's non-blocking AND never returns a 0 byte read len when its entropy is depleted. Try cat /dev/random (I am not saying this behavior is good, just that it is.) -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message