From: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
---|---|
To: | Matt Davies <matt(at)mattdavies(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Scaling further up |
Date: | 2004-03-15 22:47:50 |
Message-ID: | 1079390869.1256.1.camel@ws12.commsecure.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 2004-03-16 at 07:28, Matt Davies wrote:
> This is the preferred method, but you could create a memory disk if running
> linux. This has several caveats, though.
>
> 1. You may have to recompile the kernel for support.
> 2. You must store the database on a hard drive partition during reboots.
> 3. Because of #2 this option is generally useful if you have static content that
> is loaded to the MD upon startup of the system.
And 4. You use twice as much memory - one lot for the FS, the second for
buffer cache.
It's generally going to be slower than simply doing some typical queries
to preload the data into buffer cache, I think.
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Rosser Schwarz | 2004-03-15 23:20:32 | Re: atrocious update performance |
Previous Message | Rod Taylor | 2004-03-15 21:54:35 | Re: atrocious update performance |