Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 86F082E0125 for ; Wed, 12 Dec 2007 08:27:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 73965-07 for ; Wed, 12 Dec 2007 08:27:27 -0400 (AST) Received: from mail-relay.rwa-net.co.uk (mail-relay.rwa-net.co.uk [62.189.139.18]) by postgresql.org (Postfix) with ESMTP id 2148B2E00A0 for ; Wed, 12 Dec 2007 08:27:27 -0400 (AST) Received: from saturn.rwa-net.co.uk (saturn.rwa-net.co.uk [62.189.139.33]) by mail-relay.rwa-net.co.uk (Postfix) with ESMTP id A8C4F7D61EE for ; Wed, 12 Dec 2007 12:08:15 +0000 (GMT) Received: from [127.0.0.1] by saturn.rwa-net.co.uk (GMS 14.01.3539/NT4698.00.83343e8d) with ESMTP id diofgaaa for pgsql-performance@postgresql.org; Wed, 12 Dec 2007 12:27:24 +0000 Message-ID: <475FD3AC.1030207@rwa-net.co.uk> Date: Wed, 12 Dec 2007 12:27:24 +0000 From: Matthew Lunnon Reply-To: mlunnon@rwa-net.co.uk Organization: RWA User-Agent: Thunderbird 1.5.0.13 (Windows/20070809) MIME-Version: 1.0 To: Sven Geisler CC: pgsql-performance@postgresql.org Subject: Re: Limited performance on multi core server References: <475FB50B.8060701@rwa-net.co.uk> <475FCF1E.7030608@aeccom.com> In-Reply-To: <475FCF1E.7030608@aeccom.com> Content-Type: multipart/alternative; boundary="------------010404000002070603040302" X-AuthenticatedSender: mlunnon@rwa-net.co.uk X-Info: UNKNOWN-USER X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/173 X-Sequence-Number: 27989 This is a multi-part message in MIME format. --------------010404000002070603040302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Sven, yes the patch would be great if you could send it to me, we have already had to compile postgres to up the number of function parameters from 32 to 64. Meanwhile I will try and persuade my colleagues to consider the upgrade option. Thanks Matthew Sven Geisler wrote: > Hi Matthew, > > I remember that I also an issue with AMD Opterons before Pg 8.1 > There is a specific Opteron behaviour on shared memory locks which adds > a extra "penalty" during the execution time for Pg code before 8.1. > I can you provide my patch for Pg 8.0 which should be adaptable for Pg > 7.4 if you can compile PostgreSQL. > > But if you can upgrade you should upgrade to Pg 8.2.5 64-bit. The scale > up for your concurrent queries will be great. > > Sven. > > Matthew Lunnon schrieb: > >> Hi, >> >> I have a 4 * dual core 64bit AMD OPTERON server with 16G of RAM, running >> postgres 7.4.3. This has been recompiled on the server for 64 stored >> procedure parameters, (I assume this makes postgres 64 bit but are not >> sure). When the server gets under load from database connections >> executing reads, lets say 20 - 40 concurrent reads, the CPU's seem to >> limit at about 30-35% usage with no iowait reported. If I run a simple >> select at this time it takes 5 seconds, the same query runs in 300 >> millis when the server is not under load so it seems that the database >> is not performing well even though there is plenty of spare CPU. There >> does not appear to be large amounts of disk IO and my database is about >> 5.5G so this should fit comfortably in RAM. >> >> changes to postgresql.sql: >> >> max_connections = 500 >> shared_buffers = 96000 >> sort_mem = 10240 >> effective_cache_size = 1000000 >> >> Does anyone have any ideas what my bottle neck might be and what I can >> do about it? >> >> Thanks for any help. >> >> Matthew. >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 6: explain analyze is your friend >> > > -- Matthew Lunnon Technical Consultant RWA Ltd. mlunnon@rwa-net.co.uk Tel: +44 (0)29 2081 5056 www.rwa-net.co.uk -- --------------010404000002070603040302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Sven,

yes the patch would be great if you could send it to me, we have already had to compile postgres to up the number of function parameters from 32 to 64.

Meanwhile I will try and persuade my colleagues to consider the upgrade option.

Thanks
Matthew

Sven Geisler wrote: 
Hi Matthew,

I remember that I also an issue with AMD Opterons before Pg 8.1
There is a specific Opteron behaviour on shared memory locks which adds
a extra "penalty" during the execution time for Pg code before 8.1.
I can you provide my patch for Pg 8.0 which should be adaptable for Pg
7.4 if you can compile PostgreSQL.

But if you can upgrade you should upgrade to Pg 8.2.5 64-bit. The scale
up for your concurrent queries will be great.

Sven.

Matthew Lunnon schrieb:
  
Hi,

I have a 4 * dual core 64bit AMD OPTERON server with 16G of RAM, running
postgres 7.4.3.  This has been recompiled on the server for 64 stored
procedure parameters, (I assume this makes postgres 64 bit but are not
sure).  When the server gets under load from database connections
executing reads, lets say 20 - 40 concurrent reads, the CPU's seem to
limit at about 30-35% usage with no iowait reported. If I run a simple
select at this time it takes 5 seconds, the same query runs in 300
millis when the server is not under load so it seems that the database
is not performing well even though there is plenty of spare CPU.  There
does not appear to be large amounts of disk IO and my database is about
5.5G so this should fit comfortably in RAM.

changes to postgresql.sql:

max_connections = 500
shared_buffers = 96000
sort_mem = 10240
effective_cache_size = 1000000

Does anyone have any ideas what my bottle neck might be and what I can
do about it?

Thanks for any help.

Matthew.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
    

  

-- 
Matthew Lunnon
Technical Consultant
RWA Ltd.

 mlunnon@rwa-net.co.uk
 Tel: +44 (0)29 2081 5056
 www.rwa-net.co.uk
--
--------------010404000002070603040302--