Re: Indexes on RAM disk = insanity?
От | Richard_D_Levine@raytheon.com |
---|---|
Тема | Re: Indexes on RAM disk = insanity? |
Дата | |
Msg-id | OF27C7D6BC.D31BF71D-ON0525704D.005776A0-0525704D.0057AFE9@ftw.us.ray.com обсуждение исходный текст |
Ответ на | Indexes on RAM disk = insanity? (Steve Lane <slane@soliantconsulting.com>) |
Список | pgsql-admin |
> RAM appears to be the bottleneck -- lots > of swaps in and out. > can we put the database indexes on a RAM disk? Can you increase the RAM in the machine? I guess I should assume you're maxed out. Rick pgsql-admin-owner@postgresql.org wrote on 07/29/2005 10:32:28 AM: > All: > > We have a postgres 7.4 server where we're trying to achieve some speedups. > Right now, at least superficially, RAM appears to be the bottleneck -- lots > of swaps in and out. > > There is another consultant beside myself in the mix and he asked this > question: can we put the database indexes on a RAM disk? Won't that speed > things up? > > My first instinct is NEVER NEVER NEVER to put any database data in volatile > storage like that. But on second thought, I thought I'd ask. Is this crazy? > If one did it, how would you handle repopulating the indexes if the RAM > disk were lost? Just have a shell script that would do that automatically? > Or will postgres 8 rebuild an index if it doesn't find it where it expects? > > I recognize, or think I do, that PG 8 tablespaces would be required to > accomplish this. > > Would this be insane? Has anyone done it? > > > -------- > Steve Lane > Vice President > Soliant Consulting, Inc. > (312) 850-3830 (V) > (312) 850-3930 (F) > slane@soliantconsulting.com > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly
В списке pgsql-admin по дате отправления: