From owner-freebsd-stable@FreeBSD.ORG Thu Feb 9 02:46:00 2012 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 632C6106566C; Thu, 9 Feb 2012 02:46:00 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2DDDB8FC14; Thu, 9 Feb 2012 02:46:00 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RvK11-000Gab-Kg; Wed, 08 Feb 2012 21:45:43 -0500 Date: Wed, 8 Feb 2012 21:45:43 -0500 From: Gary Palmer To: Andriy Gapon , Jeremy Chadwick Message-ID: <20120209024543.GD10082@in-addr.com> References: <4F310C5A.6070400@norma.perm.ru> <4F310E75.7090301@FreeBSD.org> <4F3144A9.2000505@norma.perm.ru> <4F314892.50806@FreeBSD.org> <4F314B5B.100@norma.perm.ru> <4F3186C6.8000904@FreeBSD.org> <4F324F10.2060508@norma.perm.ru> <4F32DB30.6020600@FreeBSD.org> <20120208205000.GA25700@icarus.home.lan> <4F32E68A.5060607@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F32E68A.5060607@FreeBSD.org> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: "Eugene M. Zheganin" , freebsd-stable Subject: Re: zfs arc and amount of wired memory 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, 09 Feb 2012 02:46:00 -0000 On Wed, Feb 08, 2012 at 11:18:02PM +0200, Andriy Gapon wrote: > on 08/02/2012 22:50 Jeremy Chadwick said the following: > > Politely -- recommending this to a user is a good choice of action, but > > the problem is that no user, even an experienced user, is going to know > > what all of the "Types" (vmstat -m) or "ITEMs" (vmstat -z) correlate > > with on the system. > > I see no problem with users sharing the output and asking for help interpreting > it. I do not know of any easier way to analyze problems like this one. Also, since we are looking for gigs of memory it should be relatively easy to look down the 'Size' or 'MemUse' columns and identify likely candidates for "eating gobs of memory". The user doesn't need to know what the rest of the data means, and can ask what that line means and how to fix it Gary