From owner-freebsd-current@FreeBSD.ORG Tue Oct 16 20:08:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7966316A46E for ; Tue, 16 Oct 2007 20:08:33 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 90BA913C491 for ; Tue, 16 Oct 2007 20:08:31 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 16 Oct 2007 20:08:30 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO mobileKamikaze.norad) [129.13.72.169] by mail.gmx.net (mp035) with SMTP; 16 Oct 2007 22:08:30 +0200 X-Authenticated: #5465401 X-Provags-ID: V01U2FsdGVkX197JPI+tT17OLO7xdRqd3dn14/71yddq0xnfkz7wR cNA5IvXFKe083Q Message-ID: <47151A37.8020301@gmx.de> Date: Tue, 16 Oct 2007 22:08:23 +0200 From: "[LoN]Kamikaze" User-Agent: Thunderbird 2.0.0.6 (X11/20071015) MIME-Version: 1.0 To: Jeff Roberson References: <47150D87.3070804@gmx.de> <47150F82.9060805@FreeBSD.org> <20071016125400.N598@10.0.0.1> In-Reply-To: <20071016125400.N598@10.0.0.1> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Tue, 16 Oct 2007 20:14:00 +0000 Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCHED_4BSD in RELENG_7 disturbs workflow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 16 Oct 2007 20:08:33 -0000 Jeff Roberson wrote: > On Tue, 16 Oct 2007, Kris Kennaway wrote: > >> [LoN]Kamikaze wrote: >>> I know that RELENG_7 is not considered very near-release, but I >>> thought I'd >>> give my 2ยข in the hope that I might have a little influence on the >>> scheduler >>> development to my benefit. >>> >>> The switch from RELENG_6 to RELENG_7 went relatively smooth and apart >>> from ipw >>> causing panics. However there is one thing that's disturbing and this >>> is the >>> scheduler. I only have single core machines, so whatever I say only >>> applies to >>> those. If you think single-core machines are no longer important, >>> feel free to >>> ignore this. In deed, just ignore me however much you like. >>> >>>> From my perspective scheduling on RELENG_6 was way better. Even on a >>>> full >>> workload like a portupgrade the focused application (both in X and on >>> the >>> console) always received enough cycles to run smoothly and >>> applications that >>> ran in background like audio players also kept on running fine. >>> >>> Quite the contrary on RELENG_7. During a portupgrade or even worse >>> 'pkgdb -L' >>> (recovering lost dependencies) audio players (both graphical and >>> mplayer) >>> scatter, either because they don't get the hard-disk or CPU-cycles >>> (which one, >>> I don't know) and the focused application also often hangs. It just >>> looks like >>> occasionally (under load) everything freezes for a second and then >>> goes on >>> relatively normal. >>> >>> I've got the impression that things compile a little faster (that >>> might be my >>> imagination, though), but I'd rather have a smooth working experience. >>> >>> This is just my view of the situation and I suppose it is only one of >>> many. I >>> bid you be merciful with us single-core people, who cannot afford a >>> slick >>> multi-core machine, because we worry how to pay for our food at the >>> end of the >>> month. >> >> Not to say that any problems that might have developed with SCHED_4BSD >> should not be fixed, but you should give SCHED_ULE a try since it >> brings benefits even for single CPU systems (e.g. better interactive >> response). > > It would indeed be good to know if ULE improves things for you. > However, there have been a number of other reports about non-scheduler > related regressions with x windows on 7.0. I run 7.0 on a UP laptop > without difficulty. I wonder if it has something to do with a > particular device or driver. > > Jeff Well, I'll certainly see soon. However I have switched from Xorg 7.2 to 7.3 first and that worked fine. Only after the update RELENG_6 to RELENG_7 did those issues appear. I have now recompiled all my 700+ ports to rule out compatibility problems (I had lots of panics before I did that, now everything is stable, unless I try to use my wireless device) and the performance issue remains.