From: | "Gregory Maxwell" <gmaxwell(at)gmail(dot)com> |
---|---|
To: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Support Parallel Query Execution in Executor |
Date: | 2006-04-09 21:04:06 |
Message-ID: | e692861c0604091404g7f8fbf0ayec135086da03e128@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 4/9/06, Luke Lonergan <llonergan(at)greenplum(dot)com> wrote:
> Gregory,
>
> On 4/9/06 1:36 PM, "Gregory Maxwell" <gmaxwell(at)gmail(dot)com> wrote:
>
> > It might also be interesting for someone with the right testing rig on
> > linux to try the adaptive
> > readahead patch to see if that improves PG's ability to keep the disk busy.
>
> "the" adaptive readahead patch? Did I miss one?
>
> We will happily test experimental patches that improve I/O utilitization.
> We have an assortment of gear with high speed I/O, mostly Linux now.
Linux kernel patch, I'd mentioned it in a prior post.
http://www.vanheusden.com/ara/
It increases Linux's maximum readahead from 128K to 1meg .. and it
should be smart enough that you could crank it up further without too
much risk of hurting performance elsewhere.
If PG's bottlenecked on seqscan due to insufficient readahead, I'd
expect this to show an improvement... although I am still somewhat
doubtful that it'll be enough to keep the disk saturated if PG's
behavior is highly unoptimal.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-09 21:54:56 | Re: Support Parallel Query Execution in Executor |
Previous Message | Luke Lonergan | 2006-04-09 20:59:40 | Re: Support Parallel Query Execution in Executor |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-09 21:19:00 | Re: [WIP] Add relminxid column to pg_class |
Previous Message | Luke Lonergan | 2006-04-09 20:59:40 | Re: Support Parallel Query Execution in Executor |