| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Summaries on SSD usage? |
| Date: | 2011-09-02 04:58:10 |
| Message-ID: | CAOR=d=3CmzYAGGgwKRJLdWugX+AanCK7CR9L2zQfnxVP64BeHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Aug 30, 2011 at 11:23 AM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
> Hi,
>
> I'm looking for summaries (or best practices) on SSD usage with PostgreSQL.
> My use case is mainly a "read-only" database.
> Are there any around?
How big is your DB?
What kind of reads are most common, random access or sequential?
How big of a dataset do you pull out at once with a query.
SSDs are usually not a big winner for read only databases.
If the dataset is small (dozen or so gigs) get more RAM to fit it in
If it's big and sequentially accessed, then build a giant RAID-10 or RAID-6
If it's big and randomly accessed then buy a bunch of SSDs and RAID them
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkat Balaji | 2011-09-02 05:46:16 | Re: Re: How to track number of connections and hosts to Postgres cluster |
| Previous Message | Jesper Krogh | 2011-09-02 04:14:50 | Re: Summaries on SSD usage? |