| From: | Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tomas Vondra <tv(at)fuzzy(dot)cz>, Ketema <ketema(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Hardware for PostgreSQL |
| Date: | 2007-11-02 00:26:54 |
| Message-ID: | 1193963214.9625.3.camel@neuromancer.home.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2007-11-01 at 11:16 -0700, Steve Crawford wrote:
> Magnus Hagander wrote:
> > Ow Mun Heng wrote:
> >>> You're likely better off (performance-wise) putting it on the same disk
> >>> as the database itself if that one has better RAID, for example.
> >> I'm thinking along the lines of since nothing much writes to the OS
> >> Disk, I should(keyword) be safe.
> >
> > Unless it's *always* in the cache (not so likely), reads will also move
> > the heads...
>
> And if you aren't mounted noatime, reads will also cause a write.
/dev/VolGroup00/LogVol01 / ext3 defaults,noatime 1 1
/dev/md0 /raid1_array ext3 noatime,data=writeback 1 1
Yep..yep..
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Floyd | 2007-11-02 01:15:22 | hardware for PostgreSQL |
| Previous Message | Tom Lane | 2007-11-01 21:41:58 | Re: How to avoid hashjoin and mergejoin |