From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Gregory Maxwell" <gmaxwell(at)gmail(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-10 19:09:26 |
Message-ID: | C05FFB76.213EE%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Gregory,
On 4/9/06 2:04 PM, "Gregory Maxwell" <gmaxwell(at)gmail(dot)com> wrote:
> 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.
Interesting - we are now routinely using the "blockdev --setra" to set the
block device readahead and our common setting now is 16MB, so I will look at
how the behavior of this adaptive readahead affects normal query workload.
From the patch:
Normally, the kernel uses a stock readahead logic that is well
understood and well tuned. This option enables a much complex and
feature rich one. It is more aggressive and memory efficient in
doing readahead, and supports some less-common access patterns such
as reading backward and reading sparsely. However, due to the great
diversity of real world applications, it might not fit everyone.
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-04-10 19:41:59 | Re: Role incompatibilities |
Previous Message | Luke Lonergan | 2006-04-10 19:02:56 | Re: Support Parallel Query Execution in Executor |
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2006-04-11 00:05:09 | schema-qualified SET CONSTRAINTS |
Previous Message | Luke Lonergan | 2006-04-10 19:02:56 | Re: Support Parallel Query Execution in Executor |