Date: Mon, 27 Oct 2008 16:14:08 -0400 From: "Simon Chang" <simonychang@gmail.com> To: "Bill Moran" <wmoran@potentialtech.com> Cc: FreeBSD <freebsd@optiksecurite.com>, freebsd-questions@freebsd.org Subject: Re: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC Message-ID: <8efc42630810271314n3d2c97e6w14f682af14437cfc@mail.gmail.com> In-Reply-To: <20081027160522.bd32e714.wmoran@potentialtech.com> References: <49060AE0.3000301@optiksecurite.com> <8efc42630810271157u2202e7f7xfb89a7004d072ae9@mail.gmail.com> <4906196C.8000407@optiksecurite.com> <20081027160522.bd32e714.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Raising PMAP_SHPGPERPROC works most of the time. You can also re-tune > your Apache setting to keep processes from constantly spawning and > dying. For example, set the max spare and min spare servers settings > higher, so Apache keeps more spare servers around instead of spawning > them on demand and killing them when the demand ends. > > Another option is to upgrade to 7.X, which seems to have replaced the > mechanism by which this is done to be more dynamic and not have this > problem. Since he has only this server as production, and does not like re-compiling the kernel on it (and rebooting), the only option that's sensible is retuning Apache and restart services (since an upgrade to 7.X would be even more involved than a kernel rebuild). By the way, does anyone know whether there is any way to tune PMAP_SHPGPERPROC using sysctl, or does such button/knob not exist? SC
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8efc42630810271314n3d2c97e6w14f682af14437cfc>