Re: Large tables (was: RAID 0 not as fast as expected)

From: mark(at)mark(dot)mielke(dot)cc
To: Luke Lonergan <llonergan(at)greenplum(dot)com>
Cc: Bucky Jordan <bjordan(at)lumeta(dot)com>, "Spiegelberg, Greg" <gspiegelberg(at)cranel(dot)com>, Joshua Drake <jd(at)commandprompt(dot)com>, "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Large tables (was: RAID 0 not as fast as expected)
Date: 2006-09-19 03:45:47
Message-ID: 20060919034547.GA24692@mark.mielke.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Sep 18, 2006 at 06:10:13PM -0700, Luke Lonergan wrote:
> Also be sure to set the random_page_cost parameter in
> postgresql.conf to 100 or even higher when you use indexes, as the actual
> seek rate for random access ranges between 50 and 300 for modern disk
> hardware. If this parameter is left at the default of 4, indexes will often
> be used inappropriately.

Does a tool exist yet to time this for a particular configuration?

Cheers,
mark

--
mark(at)mielke(dot)cc / markm(at)ncf(dot)ca / markm(at)nortel(dot)com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada

One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...

http://mark.mielke.cc/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Luke Lonergan 2006-09-19 04:01:45 Re: Large tables (was: RAID 0 not as fast as
Previous Message Luke Lonergan 2006-09-19 03:42:39 Re: Large tables (was: RAID 0 not as fast as