From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 13:10:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 096C9C40 for ; Thu, 12 Jun 2014 13:10:55 +0000 (UTC) Received: from nmsh3.e.nsc.no (nmsh3.e.nsc.no [193.213.121.74]) by mx1.freebsd.org (Postfix) with ESMTP id 4DDBF29CF for ; Thu, 12 Jun 2014 13:10:53 +0000 (UTC) Received: from terraplane.org (ti0027a400-1392.bb.online.no [83.109.176.119]) by nmsh3.nsc.no (8.14.7/8.14.7) with ESMTP id s5CCwtF4009782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 12 Jun 2014 14:58:56 +0200 (MEST) Received: from terraplane.org (localhost [127.0.0.1]) by terraplane.org (8.14.5/8.14.5) with ESMTP id s5CCxnQw026292; Thu, 12 Jun 2014 14:59:49 +0200 (CEST) (envelope-from rumrunner@terraplane.org) Received: (from rumrunner@localhost) by terraplane.org (8.14.5/8.13.8/Submit) id s5CCxmY6026291; Thu, 12 Jun 2014 14:59:48 +0200 (CEST) (envelope-from rumrunner) Date: Thu, 12 Jun 2014 14:59:48 +0200 From: Eivind Evensen To: George Mitchell Subject: Re: Not to beat a dead horse, but ... Message-ID: <20140612125948.GB22660@klump.hjerdalen.lokalnett> References: <5394A848.7030609@m5p.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5394A848.7030609@m5p.com> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2014 13:10:55 -0000 On Sun, Jun 08, 2014 at 02:15:36PM -0400, George Mitchell wrote: > Since the majority of my systems are uniprocessors and I like to > run dnetc, SCHED_ULE has been a dealbreaker for me since day one. > Consequently I can't use freebsd_update. > > The party line seems to be, "Well, everybody knows SCHED_ULE sucks > on uniprocessors." Hello? Not everybody has upgraded to multiple > core or hyperthreaded processors yet. Do we really want to write > off every uniprocessor piece of hardware out here? > > The other assertion I hear is that SCHED_ULE really excels on some > unspecified workload or other. I'd love to see exactly how much > better it does than 4BSD on these mythological loads. -- George It doesn't seem to be only for uniprocessor systems 4BSD is the better choice. Another time when the schedulers were discussed on these lists, I checked first the ULE one which I was using, then 4BSD with a workload I knew rendered the two core machine close to unusable. I simply disconnected power to get some unclean filesystems and then tried to use the machine while the background filesystem check was running. Usage was running texteditors, X, ssh, browsers and the like. 4BSD performed better. The machine was almost usable with a little patience. Since then I've usually changed to 4BSD on other machines aswell, and at least on one 4 core machine, I notice that according to top, load is spread more even among the processors. While compiling base and some ports at the same time I've seen ULE keeping one processor busy while the others are close to 100 % idle, while 4BSD seems to keep all atleast halfway busy. I don't have any numbers other than that though, changing to 4BSD comes more from how I've the experienced using the system with each of them feels like. Eivind N Evensen