From owner-freebsd-stable@FreeBSD.ORG Tue Oct 26 14:00:02 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 56E68106564A for ; Tue, 26 Oct 2010 14:00:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by mx1.freebsd.org (Postfix) with ESMTP id EA49D8FC12 for ; Tue, 26 Oct 2010 14:00:01 +0000 (UTC) Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta01.westchester.pa.mail.comcast.net with comcast id PNZW1f0081ap0As51S018C; Tue, 26 Oct 2010 14:00:01 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta22.westchester.pa.mail.comcast.net with comcast id PS001f00F3LrwQ23iS01XZ; Tue, 26 Oct 2010 14:00:01 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 699199B422; Tue, 26 Oct 2010 06:59:59 -0700 (PDT) Date: Tue, 26 Oct 2010 06:59:59 -0700 From: Jeremy Chadwick To: Erik Trulsson Message-ID: <20101026135959.GA35363@icarus.home.lan> References: <20101026132354.GA79188@owl.midgard.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101026132354.GA79188@owl.midgard.homeip.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: rpcbind, rpc.statd memory footprint 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, 26 Oct 2010 14:00:02 -0000 On Tue, Oct 26, 2010 at 03:23:54PM +0200, Erik Trulsson wrote: > On Tue, Oct 26, 2010 at 03:08:06PM +0200, Ivan Voras wrote: > > I'm not sure what to expect from these (i.e. what is "normal" in this > > case?) but the VM sizes for the NFS-used rpc.statd and rpcbind here look > > a bit too big, compared to their resident sizes: > > > > 778 root 1 44 0 26420K 3256K select 1 0:01 0.00% > > rpcbind > > 891 root 1 44 0 263M 1296K select 1 0:01 0.00% > > rpc.statd > > > > This is 8-stable amd64. Could there be a memory leak somewhere, > > especially in rpc.statd? > > FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LEAK > > (Short version: That is expected behaviour from rpc.statd) Plus, that's 263MB of SIZE/VSZ, not RES/RSS. A portion of it could also be utilised by ELF shared object stuff (dynamic linking): $ ldd /usr/sbin/rpc.statd /usr/sbin/rpc.statd: librpcsvc.so.5 => /usr/lib/librpcsvc.so.5 (0x60648000) libc.so.7 => /lib/libc.so.7 (0x60750000) Bottom line: don't worry "too" much about VSZ when it comes to memory usage. Bloated RSS is reason to worry. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |