Date: Thu, 13 Mar 2008 10:36:28 -0400 From: Michael Proto <mike@jellydonut.org> To: Stephen.Clark@seclark.us Cc: freebsd-stable@freebsd.org Subject: Re: Approaching the limit on PV entries Message-ID: <47D93BEC.8000802@jellydonut.org> In-Reply-To: <47D91998.9030607@seclark.us> References: <fr69hn$q0o$1@ger.gmane.org> <20080312215624.GR67856@elvis.mu.org> <47D91998.9030607@seclark.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen Clark wrote: > Alfred Perlstein wrote: >> * Ivan Voras <ivoras@freebsd.org> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D93BEC.8000802>