From owner-freebsd-current@FreeBSD.ORG  Mon Sep 20 14:10:23 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1233)
	id B46F9106566C; Mon, 20 Sep 2010 14:10:23 +0000 (UTC)
Date: Mon, 20 Sep 2010 14:10:23 +0000
From: Alexander Best <arundel@freebsd.org>
To: David Xu <davidxu@freebsd.org>
Message-ID: <20100920141023.GA27509@freebsd.org>
References: <4C961009.6080609@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C961009.6080609@freebsd.org>
Cc: freebsd-current@freebsd.org
Subject: Re: sysctl -a is slow
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Sep 2010 14:10:23 -0000

On Sun Sep 19 10, David Xu wrote:
> just typed sysctl -a on keyboard, and found it is slow, sometimes
> it has been stuck for a few seconds, further studied,I found it is
> stucked at sysctl kern.geom:
> 
> %/usr/bin/time sysctl -a kern.geom
> kern.geom.collectstats: 1
> kern.geom.debugflags: 0
> kern.geom.label.debug: 0
> kern.geom.label.ext2fs.enable: 1
> kern.geom.label.iso9660.enable: 1
> kern.geom.label.msdosfs.enable: 1
> kern.geom.label.ntfs.enable: 1
> kern.geom.label.reiserfs.enable: 1
> kern.geom.label.ufs.enable: 1
> kern.geom.label.ufsid.enable: 1
> kern.geom.label.gptid.enable: 1
> kern.geom.label.gpt.enable: 1
>        2.01 real         0.00 user         0.00 sys
> 
> it seems it needs more than 2 seconds to complete.

have you had a look at the bug database? just noticed a few sysctl reports
there which describe issues similar to yours.

#134231 e.g.

cheers.
alex

> 

-- 
a13x