From owner-freebsd-stable@FreeBSD.ORG Tue Oct 16 19:53:01 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1644016A417; Tue, 16 Oct 2007 19:53:01 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id C949513C49D; Tue, 16 Oct 2007 19:53:00 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [192.168.1.104] (cpe-66-91-190-165.hawaii.res.rr.com [66.91.190.165]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l9GJqu8k002127 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2007 15:52:58 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Tue, 16 Oct 2007 12:55:35 -0700 (PDT) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: Kris Kennaway In-Reply-To: <47150F82.9060805@FreeBSD.org> Message-ID: <20071016125400.N598@10.0.0.1> References: <47150D87.3070804@gmx.de> <47150F82.9060805@FreeBSD.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2127808575-1192564535=:598" Cc: "\[LoN\]Kamikaze" , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCHED_4BSD in RELENG_7 disturbs workflow X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2007 19:53:01 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2127808575-1192564535=:598 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE 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=C2=A2 in the hope that I might have a little influence on the= =20 >> scheduler >> development to my benefit. >>=20 >> The switch from RELENG_6 to RELENG_7 went relatively smooth and apart fr= om=20 >> ipw >> causing panics. However there is one thing that's disturbing and this is= =20 >> the >> scheduler. I only have single core machines, so whatever I say only appl= ies=20 >> to >> those. If you think single-core machines are no longer important, feel f= ree=20 >> to >> ignore this. In deed, just ignore me however much you like. >>=20 >>> From my perspective scheduling on RELENG_6 was way better. Even on a fu= ll >> workload like a portupgrade the focused application (both in X and on th= e >> console) always received enough cycles to run smoothly and applications= =20 >> that >> ran in background like audio players also kept on running fine. >>=20 >> Quite the contrary on RELENG_7. During a portupgrade or even worse 'pkgd= b=20 >> -L' >> (recovering lost dependencies) audio players (both graphical and mplayer= ) >> scatter, either because they don't get the hard-disk or CPU-cycles (whic= h=20 >> one, >> I don't know) and the focused application also often hangs. It just look= s=20 >> like >> occasionally (under load) everything freezes for a second and then goes = on >> relatively normal. >>=20 >> I've got the impression that things compile a little faster (that might = be=20 >> my >> imagination, though), but I'd rather have a smooth working experience. >>=20 >> This is just my view of the situation and I suppose it is only one of ma= ny.=20 >> I >> bid you be merciful with us single-core people, who cannot afford a slic= k >> multi-core machine, because we worry how to pay for our food at the end = of=20 >> the >> month. > > Not to say that any problems that might have developed with SCHED_4BSD sh= ould=20 > not be fixed, but you should give SCHED_ULE a try since it brings benefit= s=20 > even for single CPU systems (e.g. better interactive response). It would indeed be good to know if ULE improves things for you. However,= =20 there have been a number of other reports about non-scheduler related=20 regressions with x windows on 7.0. I run 7.0 on a UP laptop without=20 difficulty. I wonder if it has something to do with a particular device=20 or driver. Jeff > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > --0-2127808575-1192564535=:598--