From owner-freebsd-stable@FreeBSD.ORG Fri Jun 3 04:17:57 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F93016A41C for ; Fri, 3 Jun 2005 04:17:57 +0000 (GMT) (envelope-from jpp@cloudview.com) Received: from skipjack.no-such-agency.net (skipjack.no-such-agency.net [64.142.114.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 621EF43D48 for ; Fri, 3 Jun 2005 04:17:57 +0000 (GMT) (envelope-from jpp@cloudview.com) Received: from skipjack.no-such-agency.net (localhost [127.0.0.1]) by skipjack.no-such-agency.net (Postfix) with ESMTP id 066C134D435 for ; Thu, 2 Jun 2005 21:17:55 -0700 (PDT) Received: from [192.168.2.120] (blackhole.no-such-agency.net [64.142.103.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skipjack.no-such-agency.net (Postfix) with ESMTP id 38EF634D415 for ; Thu, 2 Jun 2005 21:17:54 -0700 (PDT) Message-ID: <429FD9F1.1090503@cloudview.com> Date: Thu, 02 Jun 2005 21:17:53 -0700 From: John Pettitt User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AV-Checked: by skipjack Cc: Subject: gmirror rebuild speed limited by value of HZ? 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: Fri, 03 Jun 2005 04:17:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed that gmirror seems to rebuild disks by copying 128K every clock tick (or about 12.8 MB/sec on a 100HZ box) - changing HZ to 1000 resulted in my system being limited by the underlying disk controller speed (~ 30MB/sec between FW800 drives on the same 32 bit controller) does anybody know if this behavior was intentional ? John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFCn9nxaVyA7PElsKkRAg5PAKDzJMxykNf9nTvk/Jo4kbDtqUyhnQCgoTzu LqPZyVujZ2m4Snv5a6SMJ/Q= =YnDQ -----END PGP SIGNATURE-----