Hi all,
I upped effective_cache to 16000 KB and I could only up the
shared_buffers to 3000. Anything more and postgres would not start.
Postmaster is still using lots of CPU. pg_stat_activity shows only
query is happening at a time so the requests are probably queueing on
this one thread. Is this the right way to go?
Any other suggestions for me to figure out why Postmaster is using so much CPU?
Thanks in advance,
Chris
numnet=# select * from pg_stat_activity;
datid | datname | procpid | usesysid | usename |
current_query
| query_start
-------+---------+---------+----------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------------------------
17144 | numnet | 26120 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.02042-04
17144 | numnet | 26121 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.026025-04
17144 | numnet | 26122 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.030917-04
17144 | numnet | 26123 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.036266-04
17144 | numnet | 26124 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.041551-04
17144 | numnet | 26125 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.046449-04
17144 | numnet | 26126 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.051666-04
17144 | numnet | 26127 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.057398-04
17144 | numnet | 26128 | 103 | numnet | <IDLE>
| 2004-06-26 18:01:24.06225-04
17144 | numnet | 26129 | 103 | numnet | SELECT id,name,number,
systemid,pin,last,to,from,lastest,start,end,continue,type,status,duration
FROM logs WHERE (((from= 'me') and (to= 'you')) and (serverip=
'23.6.6.33
17144 | numnet | 26147 | 103 | numnet | <IDLE>
| 2004-06-26 18:03:46.175789-04
(11 rows)
----- Original Message -----
From: Joshua D. Drake <[EMAIL PROTECTED]>
Date: Sat, 26 Jun 2004 07:11:49 -0700
Subject: Re: [PERFORM] postgres 7.4 at 100%
To: Doug McNaught <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Hello,
Not to mention upping your effective_cache.
Doug McNaught wrote:
Chris Cheston <[EMAIL PROTECTED]> writes:
shared_buffers = 40 # min 16, at least max_connections*2, 8KB each
This is ridiculously low for any kind of production server. Try
something like 5000-10000 for a start.
-Doug
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
