On Wed, Oct 20, 2010 at 7:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I believe that for the equivalent Solaris option, we just automatically
> enable it when available. So there'd be no need for user documentation.
> However, I definitely *would* like to see some benchmarks proving that
> the change actually does something useful. I've always harbored the
> suspicion that this is just a knob to satisfy people who need knobs to
Well saving a few megabytes of kernel space memory isn't a bad thing.
But I think the major effect is on forking new processes. Having to
copy that page map is a major cost when you're talking about very
large memory footprints. While machine memory has gotten larger the 4k
page size hasn't. I don't think it's a big cost once all the processes
have been forked if you're reusing them beyond perhaps slightly more
efficient cache usage.
In response to
pgsql-hackers by date
|Next:||From: Greg Stark||Date: 2010-10-20 19:28:25|
|Subject: Re: PostgreSQL and HugePage|
|Previous:||From: David Fetter||Date: 2010-10-20 19:16:52|
|Subject: Re: WIP: extensible enums|