Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Date: 2013-09-13 21:15:53
Message-ID: 52338089.9080302@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/13/2013 01:58 PM, Merlin Moncure wrote:
> ok, points similar:
> *) master/slave config (two slaves for me)
> *) 'big' server 256GB mem, 32 core
> *) 80% approx. (perhaps more)
> *) some spacial searching (but not very much)
> *) OLTP
> *) presentation of load, although in my case it did resolve anywhere
> from 30 secs to half hour
> *) aside from the spike, 100% healthy
>
> points different
> *) application side pooling: 96 app servers, max 5 connections each
> (aside: are you using transaction mode pgbouncer?)

Yes.

> *) I saw gripes about relation extension in pg_locks

I'll check for that next time.

We're also working on seeing if we can reproduce this under test conditions.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-09-13 21:20:54 Re: Large shared_buffer stalls WAS: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Previous Message Merlin Moncure 2013-09-13 21:10:04 Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers