From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, rsmogura <rsmogura(at)softperience(dot)eu>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 2nd Level Buffer Cache |
Date: | 2011-03-22 15:24:54 |
Message-ID: | AANLkTikh+XAs8Ph5RwtzJPLo_bVc8w5LwDDEStQjEQd5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 18, 2011 at 9:19 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Mar 18, 2011 at 11:14 AM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>> Maybe the thing to focus on first is the oft-discussed "benchmark
>> farm" (similar to the "build farm"), with a good mix of loads, so
>> that the impact of changes can be better tracked for multiple
>> workloads on a variety of platforms and configurations. Without
>> something like that it is very hard to justify the added complexity
>> of an idea like this in terms of the performance benefit gained.
>
> A related area that could use some looking at is why performance tops
> out at shared_buffers ~8GB and starts to fall thereafter.
Under what circumstances does this happen? Can a simple pgbench -S
with a large scaling factor elicit this behavior?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Deep-Impact | 2011-03-22 15:33:54 | Re: Feature proposal: distinguish each PostgreSQL instance in the event log |
Previous Message | Euler Taveira de Oliveira | 2011-03-22 15:22:07 | Re: When and where do PG invoke PLs module? |