Thanks for the advice, It's one under consideration at the moment. What are
your thoughts on increasing RAM and shared_buffers?
On 6 Sep 2011, at 20:21, Alan Hodgson wrote:
> On September 6, 2011 12:11:10 PM Richard Shaw wrote:
>> 24 :)
>>
>> 4 x Intel Xeon-Neh
24 :)
4 x Intel Xeon-NehalemEX E7540-HexCore [2GHz]
On 6 Sep 2011, at 20:07, Alan Hodgson wrote:
> On September 5, 2011 03:36:09 PM you wrote:
>> After Restart
>>
>> procs ---memory-- ---swap-- -io --system--
>> -cpu-- r b swpd free buff cache si so
/
OS and Postgres on same mount point
On 6 Sep 2011, at 00:31, Scott Marlowe wrote:
> On Mon, Sep 5, 2011 at 4:36 PM, Richard Shaw wrote:
>> Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz
>> avgqu-sz await svctm %util
>> sda
Sep 2011, at 21:05, Alan Hodgson wrote:
> On September 5, 2011, Richard Shaw wrote:
> > Hi Andy,
> >
> > It's not a new issue no, It's a legacy system that is in no way ideal but
> > is also not in a position to be overhauled. Indexes are correct,
n the raid card providing some
level of resilience.
Thanks
Richard
On 5 Sep 2011, at 14:39, Andy Colson wrote:
> On 09/05/2011 05:28 AM, Richard Shaw wrote:
>>
>> Hi,
>>
>> I have a database server that's part of a web stack and is experiencing
>> prolo
Hi Craig,
Apologies, I should have made that clearer, I am using PgBouncer 1.4.1 in front
of Postgres and included the config at the bottom of my original mail
Regards
Richard
.
On 5 Sep 2011, at 11:49, Craig Ringer wrote:
> On 5/09/2011 6:28 PM, Richard Shaw wr
Hi,
I have a database server that's part of a web stack and is experiencing
prolonged load average spikes of up to 400+ when the db is restarted and first
accessed by the other parts of the stack and has generally poor performance on
even simple select queries.
There are 30 DBs in total on t
