From owner-freebsd-current@FreeBSD.ORG Sun Oct 14 15:21:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5619D2E0 for ; Sun, 14 Oct 2012 15:21:38 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 2B2288FC0C for ; Sun, 14 Oct 2012 15:21:38 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id q9EFLWSd057751; Sun, 14 Oct 2012 08:21:32 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id q9EFLVwj057750; Sun, 14 Oct 2012 08:21:31 -0700 (PDT) (envelope-from sgk) Date: Sun, 14 Oct 2012 08:21:31 -0700 From: Steve Kargl To: Jakub Lach Subject: Re: new DragonFly-3.2 scheduler and PostgreSQL comparision with FreeBSD 9.1-RC1 Message-ID: <20121014152131.GA57720@troutmask.apl.washington.edu> References: <1350153522261-5751733.post@n5.nabble.com> <5079DCCE.4020901@FreeBSD.org> <1350202187139-5751862.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1350202187139-5751862.post@n5.nabble.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sun, 14 Oct 2012 15:21:38 -0000 On Sun, Oct 14, 2012 at 01:09:47AM -0700, Jakub Lach wrote: > > "* Scheduler rewrite" > > They threw out old scheduler and have instant gains? That's > too good to be true, seeing as still some loathe ULE in > FreeBSD after all this time. > 'loathe' appears to be an interesting choice of word. I do not loathe ULE, but I also do not use ULE. Why? Because in my testing with my workloads, I found ULE to perform poorly in comparison to 4BSD. -- Steve