From owner-freebsd-stable@freebsd.org Sat Apr 7 04:30:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99EA7F8320B for ; Sat, 7 Apr 2018 04:30:49 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 66D15813D3 for ; Sat, 7 Apr 2018 04:30:47 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-20-68.dyn.iinet.net.au [115.166.20.68]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w374Uhcj071975 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 6 Apr 2018 21:30:46 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: kern.sched.quantum: Creepy, sadistic scheduler To: George Mitchell , freebsd-stable@freebsd.org References: <9FDC510B-49D0-4722-B695-6CD38CA20D4A@gmail.com> <8cfdb8a3-86a0-17ba-1e41-ff1912a30ee9@m5p.com> From: Julian Elischer Message-ID: <2d3dfb30-fb34-55e4-0572-df17ceb5f66e@freebsd.org> Date: Sat, 7 Apr 2018 12:30:37 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <8cfdb8a3-86a0-17ba-1e41-ff1912a30ee9@m5p.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2018 04:30:49 -0000 On 4/4/18 9:32 pm, George Mitchell wrote: > On 04/04/18 06:39, Alban Hertroys wrote: >> [...] >> That said, SCHED_ULE (the default scheduler for quite a while now) was designed with multi-CPU configurations in mind and there are claims that SCHED_4BSD works better for single-CPU configurations. You may give that a try, if you're not already on SCHED_4BSD. >> [...] > A small, disgruntled community of FreeBSD users who have never seen > proof that SCHED_ULE is better than SCHED_4BSD in any environment > continue to regularly recompile with SCHED_4BSD. I dread the day when > that becomes impossible, but at least it isn't here yet. -- George > for a single CPU you really should compile a kernel with SMP turned off and 4BSD scheduler. ULE is just trying too hard to do stuff you don't need.