From: Jim C. Nasby <jnasby@pervasive.com>
To: Luke Lonergan <llonergan@greenplum.com>
Cc: Mike Biamonte <mike@dbeat.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Huge Data sets, simple queries
Date: Tue, 31 Jan 2006 17:12:27 -0600
Message-ID: <20060131231227.GP95850@pervasive.com> (raw)
In-Reply-To: <C0052A49.1B62D%llonergan@greenplum.com>
References: <20060131192145.GU95850@pervasive.com>
<C0052A49.1B62D%llonergan@greenplum.com>
On Tue, Jan 31, 2006 at 02:52:57PM -0800, Luke Lonergan wrote:
> It's because your alternating reads are skipping in chunks across the
> platter. Disks work at their max internal rate when reading sequential
> data, and the cache is often built to buffer a track-at-a-time, so
> alternating pieces that are not contiguous has the effect of halving the max
> internal sustained bandwidth of each drive - the total is equal to one
> drive's sustained internal bandwidth.
>
> This works differently for RAID0, where the chunks are allocated to each
> drive and laid down contiguously on each, so that when they're read back,
> each drive runs at it's sustained sequential throughput.
>
> The alternating technique in mirroring might improve rotational latency for
> random seeking - a trick that Tandem exploited, but it won't improve
> bandwidth.
Or just work in multiples of tracks, which would greatly reduce the
impact of delays from seeking.
> > As for software raid, I'm wondering how well that works if you can't use
> > a BBU to allow write caching/re-ordering...
>
> Works great with standard OS write caching.
Well, the only problem with that is if the machine crashes for any
reason you risk having the database corrupted (or at best losing some
committed transactions).
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, llonergan@greenplum.com, mike@dbeat.com
Subject: Re: Huge Data sets, simple queries
In-Reply-To: <20060131231227.GP95850@pervasive.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