From: Greg Stark <gsstark@mit.edu>
To: Alex Turner <armtuk@gmail.com>
Cc: Mark Lewis <mark.lewis@mir3.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Brian Hurt <bhurt@janestcapital.com>
Cc: Tim Allen <tim@proximity.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: SAN performance mystery
Date: 16 Jun 2006 07:28:35 -0400
Message-ID: <87psh98hlo.fsf@stark.xeocode.com> (raw)
In-Reply-To: <33c6269f0606151658h731915d3k405b4da67c49228a@mail.gmail.com>
References: <4491D61B.9040507@proximity.com.au>
<4491D8DC.4070906@janestcapital.com>
<1751.1150410284@sss.pgh.pa.us>
<1150413917.31200.109.camel@archimedes>
<33c6269f0606151658h731915d3k405b4da67c49228a@mail.gmail.com>
"Alex Turner" <armtuk@gmail.com> writes:
> Given the fact that most SATA drives have only an 8MB cache, and your RAID
> controller should have at least 64MB, I would argue that the system with the
> RAID controller should always be faster. If it's not, you're getting
> short-changed somewhere, which is typical on linux, because the drivers just
> aren't there for a great many controllers that are out there.
Alternatively Linux is using the 1-4 gigabytes of cache available to it
effectively enough that the 64 megabytes of mostly duplicated cache just isn't
especially helpful...
I never understood why disk caches on the order of megabytes are exciting. Why
should disk manufacturers be any better about cache management than OS
authors?
In the case of RAID 5 this could actually work against you since the RAID
controller can _only_ use its cache to find parity blocks when writing.
Software raid can use all of the OS's disk cache to that end.
--
greg
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: gsstark@mit.edu, armtuk@gmail.com, mark.lewis@mir3.com, tgl@sss.pgh.pa.us, bhurt@janestcapital.com, tim@proximity.com.au
Subject: Re: SAN performance mystery
In-Reply-To: <87psh98hlo.fsf@stark.xeocode.com>
* 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