Received: from leo.pcisys.net (leo.pcisys.net [207.76.102.240]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9RJ0gP89658 for ; Sat, 27 Oct 2001 15:00:42 -0400 (EDT) (envelope-from hierophant@pcisys.net) Received: from [208.202.106.225] (moe1.meg106-225.cos.pcisys.net [208.202.106.225]) by leo.pcisys.net (8.12.1/8.12.1) via ESMTP id f9RJ0bpH022969 for ; Sat, 27 Oct 2001 13:00:37 -0600 (MDT) env-from (hierophant@pcisys.net) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Sat, 27 Oct 2001 13:00:37 -0600 Subject: Re: performance tuning From: Keary Suska To: PostgreSQL Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Archive-Number: 200110/1044 X-Sequence-Number: 16850 If I had a guess I would say the problem isn't with postgres, if your system CPU usage is 50%. I haven't had a system go over 20%, even under extreme duress. Are you by chance using Linux with a 2.4 kernel? The swap mechanism in 2.4 was terrible (it may have been fixed by now). What is you memory and virtual memory performance like? Extensive swapping could be at least partially responsible. Keary Suska Esoteritech, Inc. "Leveraging Open Source for a better Internet" > From: Sheer El-Showk > Date: Sat, 27 Oct 2001 13:58:42 -0400 (EDT) > To: , > Subject: [GENERAL] performance tuning > > Does anyone have a good reference for Postgres performance tuning. The > first thing I'm looking for is a way to determine my bottle-neck. My > system is currently running with 5-6 processes in the runqueue and 100% > cpu utilization (50% in the kernel). I'm guessing I'm cpu-bound but I'd > like to find out why (I'm doing mostly inserts, but I have a lot of > foreign keys). I know postgres has a lot of pg_stat_* tables but I'd like > to learn how to use these and other performance analysis tools. > > Thanks, > Sheer > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >