Date: Sat, 02 Oct 2004 11:25:18 -0700 From: Julian Elischer <julian@elischer.org> To: Julian Elischer <julian@elischer.org> Cc: hackers@freebsd.org Subject: Re: Wired memory monitoring Message-ID: <415EF28E.4010502@elischer.org> In-Reply-To: <415EF0F4.9060409@elischer.org> References: <20041002114846.GA23339@miranda.expro.pl> <415EF0F4.9060409@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > Jan Srzednicki wrote: > >> Hello, >> >> I am investigating some VM issues on FreeBSD. I have noticed that wired >> memory grows quite rapidly on forking lots of processes. After those >> processes exit, it drops a bit, but still can use about 100MB after >> launching 3000 processes. I think it's not a leak, as subsequent forks >> don't cause it to grow noticeably. >> >> I'm rather curious what eats all that memory. sysctl vm.zone shows some >> high values, but they're are not high in memory usage terms, even >> considering 50% (or so) efficiency of the slab allocator. >> >> The question is, are there any other memory inspecting tools that would >> allow me to see where is all that wired memory? And, are there any ways >> to control it's behaviour (eg. to free unused per-process structures and >> data)? >> >> greetings, > > Every thread allocated only shows the thread structure in the zone stats > but there is a 3 page stack allocated with it too which doesn't show up > there. this is in 5.x & 6.x.. you don't say what version you are looking at. > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?415EF28E.4010502>