Date: Tue, 26 Oct 2010 06:59:59 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: freebsd-stable@freebsd.org, Ivan Voras <ivoras@freebsd.org> Subject: Re: rpcbind, rpc.statd memory footprint Message-ID: <20101026135959.GA35363@icarus.home.lan> In-Reply-To: <20101026132354.GA79188@owl.midgard.homeip.net> References: <ia6jrk$8bb$1@dough.gmane.org> <20101026132354.GA79188@owl.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101026135959.GA35363>