| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com> |
| Cc: | "Mark Wong" <markwkm(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: file system and raid performance |
| Date: | 2008-08-07 21:30:13 |
| Message-ID: | dcc563d10808071430ja002d46x5459e535e97d5419@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Aug 7, 2008 at 2:59 PM, Andrej Ricnik-Bay
<andrej(dot)groups(at)gmail(dot)com> wrote:
> To me it still boggles the mind that noatime should actually slow down
> activities on ANY file-system ... has someone got an explanation for
> that kind of behaviour? As far as I'm concerned this means that even
> to any read I'll add the overhead of a write - most likely in a disk-location
> slightly off of the position that I read the data ... how would that speed
> the process up on average?
noatime turns off the atime write behaviour. Or did you already know
that and I missed some weird post where noatime somehow managed to
slow down performance?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrej Ricnik-Bay | 2008-08-07 21:57:39 | Re: file system and raid performance |
| Previous Message | Tom Lane | 2008-08-07 21:12:40 | Re: query planner not using the correct index |