Date: Wed, 24 May 2006 16:47:45 -0400 From: Vivek Khera <vivek@khera.org> To: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: PostgreSQL uses more memory on 6.1? Message-ID: <BFFD2986-610D-42CB-87AA-4F4740F0E4AA@khera.org> In-Reply-To: <200605241114.52666.kirk@strauser.com> References: <200605231531.18092.kirk@strauser.com> <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> <200605241114.52666.kirk@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-11-545257533 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 24, 2006, at 12:14 PM, Kirk Strauser wrote: > Is any of this stuff well documented other than in NOTES? I can > see what > each setting does, but don't really have a feel for *why* I'd need to > increase a given setting, what the drawback is to increasing it, or > why it > was so low in the first place. SYSV IPC falls into the black art part of the universe, unfortunately. You really have to dig into the application (ie, postgres in this case) to determine how much of those resources it wants. > > For that matter, why does this stuff have to be manually configured? > Couldn't the kernel automatically expand a lot of these numbers as > needed? Some are only settable at boot time because they make fixed sized structures (yes, still in this day and age...) I don't know the drawbacks of making them larger than necessary, but with multi-gig RAM servers I don't worry about it too much. --Apple-Mail-11-545257533--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFFD2986-610D-42CB-87AA-4F4740F0E4AA>