From: | Chris Travers <chris(at)travelamericas(dot)com> |
---|---|
To: | Steve Lane <slane(at)soliantconsulting(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Indexes on RAM disk = insanity? |
Date: | 2005-07-29 16:50:07 |
Message-ID: | 42EA5E3F.4090909@travelamericas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Steve Lane wrote:
>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?
>
>
I am quite wary about putting the indexes on a RAM DISK for another reason.
You say that RAM is your bottleneck, so putting anything unnecessary in
RAM seems like a good way to get less performance rather than more.
Additionally you have some overhead in tracking the files, etc. and they
will remain in RAM even when they are not used. This leaves the system
with less effective RAM for the memory intensive operations.
Such a move might make a lot of sense if you had a LOT of RAM but disk
I/O was the bottleneck. However, if a lack of RAM is your problem,
putting more stuff in RAM doesn't seem very sound to me.
Best Wishes,
Chris Travers
Metatron Technology Consulting
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Lane | 2005-07-29 17:17:42 | Re: Indexes on RAM disk = insanity? |
Previous Message | Fabio C. Bon | 2005-07-29 16:30:46 | Questions about fsync |