From owner-freebsd-stable@FreeBSD.ORG Tue Jan 12 20:27:42 2010 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 C9D05106566B for ; Tue, 12 Jan 2010 20:27:42 +0000 (UTC) (envelope-from mail@maxlor.com) Received: from mxout002.mail.hostpoint.ch (mxout002.mail.hostpoint.ch [217.26.49.181]) by mx1.freebsd.org (Postfix) with ESMTP id 8006C8FC18 for ; Tue, 12 Jan 2010 20:27:42 +0000 (UTC) Received: from [10.0.2.20] (helo=asmtp002.mail.hostpoint.ch) by mxout002.mail.hostpoint.ch with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NUnL2-000HQZ-VF for freebsd-stable@freebsd.org; Tue, 12 Jan 2010 21:27:40 +0100 Received: from [82.136.101.114] (helo=atlantis.intranet) by asmtp002.mail.hostpoint.ch with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NUnL2-0000Sk-RZ for freebsd-stable@freebsd.org; Tue, 12 Jan 2010 21:27:40 +0100 Received: from mini.localnet (vimur.intranet [10.0.0.254]) by atlantis.intranet (Postfix) with ESMTPSA id 8A9A119CB4 for ; Tue, 12 Jan 2010 21:27:40 +0100 (CET) X-Authenticated-Sender-Id: mail@maxlor.com From: Benjamin Lutz To: freebsd-stable@freebsd.org Date: Tue, 12 Jan 2010 21:27:39 +0100 User-Agent: KMail/1.12.4 (Linux/2.6.31.8-0.1-desktop; KDE/4.3.4; i686; ; ) References: <201001121050.04982.mail@maxlor.com> In-Reply-To: X-Face: $Ov27?7*N,h60fIEfNJdb!m,@#4T/d; 1hw|W0zvsHM(a$Yn6BYQ0^SEEXvi8>D`|V*F"_+ R2@Aq>+mNb4`,'[[%z9v0Fa~]AD1}xQO3|>b.z&}l#R-_(P`?@Mz"kS; XC>Eti,i3>%@g? 4f,\c7|Ghwb&ky$b2PJ^\0b83NkLsFKv|smL/cI4UD%Tu8alAD MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201001122127.39886.mail@maxlor.com> Subject: Re: Please explain FreeBSD 8.0/ZFS memory usage patterns 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: Tue, 12 Jan 2010 20:27:42 -0000 On Tuesday 12 January 2010 15:35:12 Ivan Voras wrote: > How do you get those categories: kern, proc? I suppose proc could be sum > of resident sizes of processes (aka "RES" in top) and kern could be > sysctl vm.kmem_size? yes, exactly. kern is kvm.kmem_size, proc is the sum of RSS memory of all processes (including kernel processes), active and wired are the value from top, arc is the ZFS ARC. > > In the first half of the graph, there's a torrent download running, which > > I assume causes the large fluctuations in memory usage. However, memory > > usage > > Large fluctuations in which category? The ARC? (since "proc" doesn't > fluctuate much). well, wired seems to move with the ARC. But why does active memory move so much? As you pointed out, my processes don't change that much. Cheers Benjamin