From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: Ketema <ketema@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware for PostgreSQL
Date: Fri, 02 Nov 2007 08:26:54 +0800
Message-ID: <1193963214.9625.3.camel@neuromancer.home.net> (raw)
In-Reply-To: <472A17ED.1070008@pinpointresearch.com>
References: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
<4728FAA1.7060905@fuzzy.cz>
<1193889182.7999.71.camel@neuromancer.home.net>
<4729783A.2030201@hagander.net>
<1193903161.9148.27.camel@neuromancer.home.net>
<472985B5.6010701@hagander.net>
<472A17ED.1070008@pinpointresearch.com>
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..
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Ow.Mun.Heng@wdc.com, scrawford@pinpointresearch.com, magnus@hagander.net, tv@fuzzy.cz, ketema@gmail.com
Subject: Re: Hardware for PostgreSQL
In-Reply-To: <1193963214.9625.3.camel@neuromancer.home.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox