From owner-freebsd-stable@FreeBSD.ORG Thu Oct 4 14:54:50 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 DA01616A41A for ; Thu, 4 Oct 2007 14:54:50 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id CB0D813C44B for ; Thu, 4 Oct 2007 14:54:50 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id AE441115D7; Thu, 4 Oct 2007 09:39:46 -0500 (CDT) Date: Thu, 4 Oct 2007 09:39:44 -0500 From: Craig Boston To: freebsd-stable@FreeBSD.ORG, matrix@itlegion.ru Message-ID: <20071004143944.GA46491@nowhere> Mail-Followup-To: Craig Boston , freebsd-stable@FreeBSD.ORG, matrix@itlegion.ru References: <02d401c805cb$abf59ec0$0c00a8c0@Artem> <200710041232.l94CWd6W056143@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710041232.l94CWd6W056143@lurza.secnetix.de> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: Quation about HZ kernel option 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, 04 Oct 2007 14:54:50 -0000 On Thu, Oct 04, 2007 at 02:32:39PM +0200, Oliver Fromme wrote: > In that case, I would recommend not to override the > default at all (which is 1000). ISTM that it would be better to use kern.hz=100 in this case. My reasoning is that a web server shouldn't be terribly sensitive to latency, so it's better to have longer quantums to get more work done without context switching overhead. If you're not using polling, you'll be getting interrupts for network traffic anyway. With polling on however, a high HZ value makes sense. > Basically, the kernel cannot handle time slices smaller > than 1/HZ seconds, for any purpose. It should still be able to schedule a new process for the remainder of the slice should the current one block or yield though, right? Craig