From owner-freebsd-performance@FreeBSD.ORG Mon Nov 3 11:15:27 2008 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F5AB1065690 for ; Mon, 3 Nov 2008 11:15:27 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id B49988FC12 for ; Mon, 3 Nov 2008 11:15:26 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 4B027CCCB; Mon, 3 Nov 2008 13:15:23 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15640-08; Mon, 3 Nov 2008 13:15:22 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 4D4F6CCA2; Mon, 3 Nov 2008 13:15:22 +0200 (EET) Message-ID: <490EDD49.5070902@bulinfo.net> Date: Mon, 03 Nov 2008 13:15:21 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Julian Elischer References: <000001c93b0c$6195e6b0$2f096f0a@china.huawei.com> <490AB477.2080001@bulinfo.net> <490AB750.9040505@elischer.org> In-Reply-To: <490AB750.9040505@elischer.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-performance@freebsd.org, Sam Xia Subject: Re: 1. thread switching time? (Krassimir Slavchev) 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, 03 Nov 2008 11:15:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Julian Elischer wrote: > Krassimir Slavchev wrote: > >> >> Also, I am able to set HZ=100000 but the thread switching time is still >> ~1ms. > > You must be talking about the time that a thread can run before it is > pushed out by other threads? I know I've seem many x 10,000 context > switches in some cases, i.e. look at very high interrupt rates > etc. so I guess I'm not sure what you are measuring.. > > at one time the scheduling quantum was independent of Hz. > I am not sure how true that is now.. > The scheduling quantum is independent of Hz for Hz > 1000. usr/src/sys/kern_tc.c: ... if (hz > 1000) tc_tick = (hz + 500) / 1000; else tc_tick = 1; ... I am not sure whether setting Hz > 1000 impact on performance or not, e.g using polling(4). Removing this limitation and setting kern.hz=10000 give 100usec quantum. Thanks for the point. Best Regards -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFJDt1JxJBWvpalMpkRAnWCAJ9z5Z7JYDC/3AdsJe+Cn7+dg6y3HwCdHPZA 6sK5dec43n41/QcbiluJoeA= =8u2E -----END PGP SIGNATURE-----