From owner-freebsd-performance@FreeBSD.ORG Mon Jun 12 20:01:46 2006 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C8DF16A41A; Mon, 12 Jun 2006 20:01:46 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2879043D81; Mon, 12 Jun 2006 20:01:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k5CK1YMF060726; Mon, 12 Jun 2006 14:01:41 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <448DC818.9070100@samsco.org> Date: Mon, 12 Jun 2006 14:01:28 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: danial_thom@yahoo.com References: <20060612195754.72452.qmail@web33306.mail.mud.yahoo.com> In-Reply-To: <20060612195754.72452.qmail@web33306.mail.mud.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-performance@freebsd.org, Robert Watson Subject: Re: Initial 6.1 questions X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2006 20:01:46 -0000 Danial Thom wrote: > > --- Robert Watson wrote: > > >>On Mon, 12 Jun 2006, Danial Thom wrote: >> >> >>>first, why is the default for HZ now 1000? It >> >>seems that 900 extra clock >> >>>interrupts aren't a performance enhancement. >> >>This is a design change that is in the process >>of being reconsidered. I >>expect that HZ will not be 1000 in 7.x, but >>can't tell you whether it will go >>back to 100, or some middle ground. There are >>a number of benefits to a >>higher HZ, not least is more accurate timing of >>some network timer events. >>Since I don't have my hands in the timer code, >>I can't speak to what the >>decision process here is, or when any change >>might happen, but I do expect to >>see some change. > > > Will anything break if I tweek this downward? > I run a number of high-load production systems that do a lot of network and filesystem activity, all with HZ set to 100. It has also been shown in the past that certain things in the network area where not fixed to deal with a high HZ value, so it's possible that it's even more stable/reliable with an HZ value of 100. My personal opinion is that HZ should gop back down to 100 in 7-CURRENT immediately, and only be incremented back up when/if it's proven to be the right thing to do. And, I say that as someone who (errantly) pushed for the increase to 1000 several years ago. Scott