Skip site navigation (1) Skip section navigation (2)

Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)

From: Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Yeb Havinga <yebhavinga(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)
Date: 2010-06-25 15:59:21
Message-ID: AANLkTikJEyqi_8WRI6FjH3OBnnIj4SV9EbTBLl2EGCZw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Dear List,

pgtune suggests the following:
(current value are in braces via reason) , (*) indicates significant
difference from current value.

     default_statistics_target = 50 # pgtune wizard 2010-06-25  (current 100
via default)
(*) maintenance_work_mem = 1GB # pgtune wizard 2010-06-25 (16MB via default)
     checkpoint_completion_target = 0.9 # pgtune wizard 2010-06-25 (0.5 via
default)
(*) effective_cache_size = 22GB # pgtune wizard 2010-06-25 (18GB ,
specified)
     work_mem = 192MB # pgtune wizard 2010-06-25  (256MB , specified)
(*) wal_buffers = 8MB # pgtune wizard 2010-06-25 ( 64kb , via default)
     checkpoint_segments = 16 # pgtune wizard 2010-06-25 (30 , specified)
     shared_buffers = 7680MB # pgtune wizard 2010-06-25 ( 4096 MB ,
specified)
(*) max_connections = 80 # pgtune wizard 2010-06-25 ( 300 , ;-)  specified )

when i reduce max_connections i start getting errors, i will see again
concurrent connections
during business hours. lot of our connections are in <IDLE in transaction
state> during business
this peculiar  behavior of  mod_perl servers have been discussed in past i
think. dont' remember
if there was any resolution.

In response to

Responses

pgsql-performance by date

Next:From: Rajesh Kumar MallahDate: 2010-06-25 16:07:03
Subject: Re: Occasional giant spikes in CPU load
Previous:From: Rajesh Kumar MallahDate: 2010-06-25 15:14:41
Subject: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group