From: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Julius Stroffek <Julius(dot)Stroffek(at)sun(dot)com>, pgsql-hackers(at)postgresql(dot)org, Dano Vojtek <danielkov(at)gmail(dot)com> |
Subject: | Re: Multi CPU Queries - Feedback and/or suggestions wanted! |
Date: | 2008-10-24 05:02:18 |
Message-ID: | 1F873CCC-1E30-47D4-9B28-E3140F0ADCF3@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Based on what? I did test this and posted the data. The results I
posted showed that posix_fadvise on Linux performed nearly as well on
Linux as async I/O on Solaris on identical hardware.
More importantly it scaled with the number if drives. A 15 drive array
gets about 15x the performance of a 1 drive array if enough read-ahead
is done. Plus an extra boost if the input wasn't already sorted which
presumably reflects the better i/o ordering.
--
greg
On 24 Oct 2008, at 04:29 AM, "Jonah H. Harris"
<jonah(dot)harris(at)gmail(dot)com> wrote:
> On Thu, Oct 23, 2008 at 8:44 PM, Bruce Momjian <bruce(at)momjian(dot)us>
> wrote:
>> True, it is a kludge but if it gives us 95% of the benfit with 10% of
>> the code, it is a win.
>
> I'd say, optimistically, maybe 30-45% the benefit over a proper
> multi-block read using O_DIRECT.
>
> --
> Jonah H. Harris, Senior DBA
> myYearbook.com
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2008-10-24 05:23:04 | Re: Multi CPU Queries - Feedback and/or suggestions wanted! |
Previous Message | Greg Stark | 2008-10-24 04:56:42 | Re: Multi CPU Queries - Feedback and/or suggestions wanted! |