From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 2 11:48:49 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11ED616A4CE for ; Sat, 2 Oct 2004 11:48:49 +0000 (GMT) Received: from miranda.expro.pl (mail2.expro.pl [193.25.166.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954D343D58 for ; Sat, 2 Oct 2004 11:48:48 +0000 (GMT) (envelope-from winfried@miranda.expro.pl) Received: by miranda.expro.pl (Postfix, from userid 1001) id E9CE9153F7; Sat, 2 Oct 2004 13:48:46 +0200 (CEST) Date: Sat, 2 Oct 2004 13:48:46 +0200 From: Jan Srzednicki To: hackers@freebsd.org Message-ID: <20041002114846.GA23339@miranda.expro.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Mailman-Approved-At: Sat, 02 Oct 2004 12:28:50 +0000 Subject: Wired memory monitoring X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2004 11:48:49 -0000 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, -- Jan 'Winfried' Srzednicki w@expro.pl