From owner-freebsd-current@FreeBSD.ORG Fri Oct 8 08:15:38 2004 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 E721116A4CE for ; Fri, 8 Oct 2004 08:15:38 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7697B43D41 for ; Fri, 8 Oct 2004 08:15:38 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from bsdbox.farid-hajji.net (bsdbox [192.168.254.3]) by fw.farid-hajji.net (Postfix) with ESMTP id 207DD4B598; Fri, 8 Oct 2004 10:15:36 +0200 (CEST) Date: Fri, 8 Oct 2004 10:15:55 +0200 From: cpghost@cordula.ws To: Benjamin Close Message-ID: <20041008081555.GA91773@bsdbox.farid-hajji.net> References: <200410071835.51942.marc.ramirez@bluecirclesoft.com> <4165D5CD.6020005@cs.unisa.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4165D5CD.6020005@cs.unisa.edu.au> User-Agent: Mutt/1.5.6i cc: Marc Ramirez cc: freebsd-current@freebsd.org Subject: Re: Noticable Delays Since Beta 3 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: Fri, 08 Oct 2004 08:15:39 -0000 On Fri, Oct 08, 2004 at 09:18:29AM +0930, Benjamin Close wrote: > I believe the issue is with the scheduler or something related to it. > The effect seems to occur when a process > hasn't been used for a long time and then is suddenly switched from a > wait state to an active state. Yes, that's exactly what I'm observing here. > Once the process responds it runs fine until the next long delay. It > seems more responsive with BETA7 but no where near the same as before > the scheduler change. Again, same observation here. > It might be a symptom related to X, will test overnight in console. It definitely happens in text mode console too. Just one more hint: After typing something on the console, it takes 2 to 5 seconds BEFORE there is disk activity, then there's a reply. It seems like SCHED_4BSD (?) needs some time of its own before deciding to swap the process back in (just guessing here). However, this doesn't explain why the mouse freezes in X while in motion. Perhaps when moving over a window of a long time idle process? Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/