My lab is looking into speeding up our databases beyond the tuning
that can already be done through configuration. Has anyone had
hands-on experience running postgres with PGDATA entirely in memory?
One possible configuration I can imagine is that we construct the
database on disk, then on boot create an appropriate ramdisk and
copy the whole postgres tree to the ramdisk. Then we start the
postgres daemons pointing PGDATA to the ramdisk. The database
in memory won't change (or, if it does, we don't care about saving
the changes), so there's no concern about losing changes if there's
Is this even a starter, or is postgres smart enough to use as much
memory as it's told? We'd be getting a huge chunk of RAM (over 10GB!),
so it would be possible to hold our entire database in RAM if needed.
Any pointers would be great--a first perusal of Google didn't turn
up much (just stuff on loading a database from CD-ROM into a ramdisk).
Oh, and Josh, I'd try to make an sfpug in November if I'm able, but
my wife is due to give birth, so may need to skip out unannounced. :)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom
sfpug by date
|Next:||From: William Yu||Date: 2003-10-14 23:12:22|
|Subject: Re: running postgres in a ramdisk|
|Previous:||From: Patrick Hatcher||Date: 2003-10-13 15:43:45|
|Subject: Re: Meeting, LUG in November?|