From owner-freebsd-questions@FreeBSD.ORG Wed Mar 8 22:14:43 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14B3A16A423 for ; Wed, 8 Mar 2006 22:14:43 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 429C843D48 for ; Wed, 8 Mar 2006 22:14:41 +0000 (GMT) (envelope-from peo@intersonic.se) Received: from localhost (terrapin.inter-sonic.com [172.16.1.12]) by neonpark.inter-sonic.com (Postfix) with ESMTP id 0507E818E22; Wed, 8 Mar 2006 23:14:40 +0100 (CET) Message-ID: <440F574C.9040902@intersonic.se> Date: Wed, 08 Mar 2006 23:14:36 +0100 From: Per olof Ljungmark User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Lowell Gilbert References: <440D943E.7060200@intersonic.se> <44lkvl9egk.fsf@be-well.ilk.org> In-Reply-To: <44lkvl9egk.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Out of memory during "large" request X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 22:14:43 -0000 Lowell Gilbert wrote: > Per olof Ljungmark writes: > >> FreeBSD 6-STABLE >> >> Got this when I ran a Perl script: >> Out of memory during "large" request for 33558528 bytes >> >> Would this be good syntax in /boot/loader.conf, the system has 2G RAM: >> vm.kmem_size_max=671088640 >> to try to cure the problem? Where do I best learn more about memory tuning? > > Are you sure you're not just running into process limits, as opposed > to kernel limits? Honestly, no. But on a 5.4 system I did cure the same problem with the line "kern.maxdsiz="768M"" in loader.conf and I thought "vm.kmem_size" would be the corresponding parameter in 6?