| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Clodoaldo <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> |
| Cc: | "PostgreSQL - General ML" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query planning configuration and solid state drives |
| Date: | 2008-05-30 19:02:23 |
| Message-ID: | b42b73150805301202n743ba71i1b5e31fc6c44fd81@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, May 30, 2008 at 2:55 PM, Clodoaldo
<clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> wrote:
> 2008/5/30 Merlin Moncure <mmoncure(at)gmail(dot)com>:
>> On Fri, May 30, 2008 at 11:43 AM, Clodoaldo
>> <clodoaldo(dot)pinto(dot)neto(at)gmail(dot)com> wrote:
>>> What should be changed in the query planning configuration, if at all,
>>> if a ultrafast solid state drive would be used to host a whole
>>> database ? Specially if used in Raid 0 configurations.
>>
>> random_page_cost can probably be reduced...
>>
>> is this flash ssd?
>
> Yes, flash ssd.
Then you are probably aware that sequential speeds are similar to
spinning disk, random access is much, much. (much) better, and random
write is worse.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-05-30 19:26:52 | Re: Connection problem |
| Previous Message | Clodoaldo | 2008-05-30 18:55:41 | Re: Query planning configuration and solid state drives |