From: Luke Lonergan <llonergan@greenplum.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
Date: Mon, 10 Sep 2007 13:19:03 -0700
Message-ID: <C30AF4C7.4230B%llonergan@greenplum.com> (raw)
In-Reply-To: <fc45mi$1tj9$1@news.hub.org>
Should be a lot higher, something like 10-15 is approximating accurate.
Increasing the number of disks in a RAID actually makes the number higher,
not lower. Until Postgres gets AIO + the ability to post multiple
concurrent IOs on index probes, random IO does not scale with increasing
disk count, but sequential does, thus the increasing "random page cost" as
the RAID gets faster.
The reason to change the number is to try to discourage the planner from
choosing index scans too aggressively. We (GP) have implemented something
we call "Adaptive Nested Loop" to replace a nested loop + index scan with a
hash join when the selectivity estimates are off in order to improve this
behavior. We also run with a "random_page_cost=100" because we generally
run on machines with fast sequential I/O.
- Luke
On 9/10/07 12:25 PM, "Carlo Stonebanks" <stonec.register@sympatico.ca>
wrote:
> Can anyone answer this for me: Although I realize my client's disk subsystem
> (SCSI/RAID Smart Array E200 controller using RAID 1) is less than
> impressive - is the default setting of 4.0 realistic or could it be lower?
>
> Thanks!
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
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: llonergan@greenplum.com, stonec.register@sympatico.ca
Subject: Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
In-Reply-To: <C30AF4C7.4230B%llonergan@greenplum.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