From owner-freebsd-java@FreeBSD.ORG Tue Mar 4 15:10:59 2008 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A493106566B for ; Tue, 4 Mar 2008 15:10:59 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feba:632a]) by mx1.freebsd.org (Postfix) with ESMTP id 8C13A8FC17 for ; Tue, 4 Mar 2008 15:10:58 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id m24EQoQp024338; Tue, 4 Mar 2008 15:26:51 +0100 From: Pieter de Goeje To: freebsd-java@freebsd.org Date: Tue, 4 Mar 2008 15:26:50 +0100 User-Agent: KMail/1.9.7 References: <2be802c80803040538m28db0afcm32745678ff446a58@mail.gmail.com> In-Reply-To: <2be802c80803040538m28db0afcm32745678ff446a58@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803041526.50670.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact servicedesk@icts.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Fernando Sanchez Subject: Re: Question regarding diablo-jdk X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 15:10:59 -0000 On Tuesday 04 March 2008, Fernando Sanchez wrote: > Hi! > > I have a bit of a problem with the diablo-jdk and Tomcat. See, it's > eating up all my memory, and I don't have that much of it on the > target machine. Now I see this cache being allocated at the beginning > (256 MB), and I wonder if there is a parameter to prevent this from > happening, and using a more resource-friendly way of allocating > memory. Or if there is anything else I can do, short of adding more > memory, which is not possible in my situation. What cache are you talking about? A freshly started tomcat running a simple webapp uses about 72MB resident memory on my (64bit) system. 256MB seems excessive. I am running tomcat 6 + tomcat-native on jdk16. -- Pieter de Goeje