From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 9 01:59:52 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F394C16A401 for ; Sun, 9 Apr 2006 01:59:51 +0000 (UTC) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CB5B43D45 for ; Sun, 9 Apr 2006 01:59:51 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 2E9014CD84; Sun, 9 Apr 2006 02:00:35 +0000 (GMT) Received: from [192.168.0.6] (ppp157-158.static.internode.on.net [150.101.157.158]) by p4.roq.com (Postfix) with ESMTP id 4559C4CD1D; Sun, 9 Apr 2006 02:00:34 +0000 (GMT) Message-ID: <44386A94.2060401@roq.com> Date: Sun, 09 Apr 2006 11:59:48 +1000 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: patrick References: <20060407075301.I21526@gandalf.cyberwizards.nl> In-Reply-To: <20060407075301.I21526@gandalf.cyberwizards.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: extreme mem usage under amd64 arch ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Apr 2006 01:59:52 -0000 patrick wrote: > > Hello, > > Hope someone can shine a light for me on this, > > I have several boxes running STABLE 4/5/6 > > one of them is amd64/stable6 on dual opterons. > > I notice that on this amd system the httpd 2.2 and perl 5.8.8 > binairies alocateds a lot of memory: > > 76562 www 1 20 0 156M 38528K lockf 0 0:00 0.00% > httpd > 76561 www 1 20 0 156M 38528K lockf 0 0:00 0.00% > httpd > 76830 www 1 20 0 155M 37740K lockf 0 0:00 0.00% > httpd > 76560 www 1 20 0 155M 37736K lockf 0 0:00 0.00% > httpd > 76563 www 1 4 0 155M 37736K kqread 0 0:00 0.00% > httpd > 61338 root 1 8 0 155M 37668K nanslp 0 0:02 0.00% > httpd > 73328 root 1 8 0 142M 102M nanslp 0 0:03 0.00% > perl5.8.8 > 73611 root 1 8 0 142M 101M nanslp 0 0:03 0.00% > perl5.8.8 > 75475 root 1 8 0 142M 99M nanslp 0 0:02 0.00% > perl5.8.8 > 76966 root 1 8 0 142M 99M nanslp 0 0:02 0.00% > perl5.8.8 > 75736 root 1 8 0 142M 101M nanslp 0 0:02 0.00% > perl5.8.8 > > The binairy self has normal size: > > The only big diff in this case is the AMD64 arch. > You kind of got your self worried about nothing. The servers real memory usage is the "RES" column, SIZE (where it has 156M) is the potential size it could grow before the kernel allocates it more memory and has little to do with actual real memory usage. Mike