From owner-freebsd-stable@FreeBSD.ORG Thu Mar 13 14:36:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E23D1065671 for ; Thu, 13 Mar 2008 14:36:29 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail3.secureworks.net (mail3.secureworks.net [65.114.32.155]) by mx1.freebsd.org (Postfix) with ESMTP id 46ED88FC4C for ; Thu, 13 Mar 2008 14:36:29 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from localhost (localhost [127.0.0.1]) by mail3.secureworks.net (Postfix) with ESMTP id 76FB619E3E8; Thu, 13 Mar 2008 14:36:28 +0000 (GMT) X-Virus-Scanned: amavisd-new at secureworks.net Received: from mail3.secureworks.net ([127.0.0.1]) by localhost (mail3.secureworks.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scKx7q3eYyNp; Thu, 13 Mar 2008 14:36:28 +0000 (GMT) Received: from [192.168.23.35] (mole1.secureworks.net [63.239.86.3]) by mail3.secureworks.net (Postfix) with ESMTP id 44C4419E3E1; Thu, 13 Mar 2008 14:36:28 +0000 (GMT) Message-ID: <47D93BEC.8000802@jellydonut.org> Date: Thu, 13 Mar 2008 10:36:28 -0400 From: Michael Proto User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080227 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <20080312215624.GR67856@elvis.mu.org> <47D91998.9030607@seclark.us> In-Reply-To: <47D91998.9030607@seclark.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Mar 2008 14:36:29 -0000 Stephen Clark wrote: > Alfred Perlstein wrote: >> * Ivan Voras [080311 08:46] wrote: >> >>> During heavy postgresql load (pgbench), /var/log/messages registers >>> (multiple times) the following message: >>> >>> "Approaching the limit on PV entries, consider increasing either the >>> vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl" >>> >>> I'm increasing both, but no matter what I increase them to, after a >>> short time they again get increased by the system (???). >>> >>> The values are currently: >>> >>> vm.pmap.shpgperproc: 1134 >>> vm.pmap.pv_entry_max: 8000000 >>> >>> But the last sysctl setting, verified by retrieving it from my shell >>> command line history, is that I set vm.pmap.shpgperproc to 800. >>> >>> Is this normal, and what are the common settings for these values? The >>> machine is 2x4-core, currently 4 GB RAM (which will increase to at least >>> 6 GB), amd64, running postgresql, php and apache. >>> >>> >> >> try setting: >> >> sysctl kern.ipc.shm_use_phys=1 >> >> >> >> > Could you please explain what that does and why? > > Also could someone point me to where all these sysctls are documented > other than in the source code - which lots > of time has no explanation. It would really help the average sys admin/ > user if these were documented. > > Thanks, > Steve > tuning(7) is a good place to start. -Proto