From owner-freebsd-stable@FreeBSD.ORG Thu Dec 15 07:46:25 2011 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 9BC8A106566C for ; Thu, 15 Dec 2011 07:46:25 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 208A28FC0A for ; Thu, 15 Dec 2011 07:46:24 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id pBF7kEMR000181 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 15 Dec 2011 09:46:20 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <4EE9A5C5.2070001@digsys.bg> Date: Thu, 15 Dec 2011 09:46:13 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111110 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EE1EAFE.3070408@m5p.com> <4EE2AE64.9060802@m5p.com> <4EE88343.2050302@m5p.com> <4EE933C6.4020209@zedat.fu-berlin.de> In-Reply-To: <4EE933C6.4020209@zedat.fu-berlin.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: SCHED_ULE should not be the default 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: Thu, 15 Dec 2011 07:46:25 -0000 On 15.12.11 01:39, O. Hartmann wrote: > On 12/14/11 18:54, Tom Evans wrote: >> On Wed, Dec 14, 2011 at 11:06 AM, George Mitchell >> wrote: >>> Dear Secret Masters of FreeBSD: Can we have a decision on whether to >>> change back to SCHED_4BSD while SCHED_ULE gets properly fixed? >>> >> Please do not do this. This thread has shown that ULE performs poorly >> in very specific scenarios where the server is loaded with NCPU+1 CPU >> bound processes, and brought forward more complaints about >> interactivity in X (I've never noticed this, and use a FreeBSD desktop >> daily). > I would highly appreciate a decission against SCHED_ULE as the default > scheduler! SCHED_4BSD is considered a more mature entity and obviously > it seems that SCHED_ULE needs some refinements to achieve a better level > of quality. > My logic would be, if SCHED_ULE works better on multi-CPU systems, or if SCHED_4BSD works poor on multi-CPU systems, then by all means keep SCHED_ULE as default scheduler. We are at the end of 2011 and the number of single or dual core CPU systems is decreasing. Most people would just try the newest FreeBSD version on their newest hardware and on that base make an "informed" decision if it is worth it. If on newer hardware SCHED_ULE gives better performance, then again it should be the default. Then, FreeBSD is used in an extremely wide set fo different environments. What scheduler might benefit an one CPU, simple architecture X workstation may be damaging for the performance of multiple CPU, NUMA based server with a large number of non-interactive processes running. Perhaps an knob should be provided with sufficient documentation for those that will not go forward to recompile the kernel (the majority of users, I would guess). I tried switching my RELENG8 desktop from SCHED_ULE to SCHED_4BSD yesterday and cannot see any measurable difference in responsiveness. My 'stress test' is typically an FLASH game, that get's firefox in an almost unresponsive state, eats one of the CPU cores -- but no difference. Well, FLASH has it's own set of problems on FreeBSD, but these are typical "desktop" uses. Running 100% compute intensive processes in background is not. Daniel PS: As to why Linux is "better" in these usages: they do not care much to do things "right", but rather to achieve performance. In my opinion, most of us are with FreeBSD for the "do it right" attitude.