pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jérôme BENOIS <benois@argia-engineering.fr>
To: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-performance@postgresql.org, Xavier Milliard <milliard@argia.fr>
Subject: Re: High CPU Load
Date: Fri, 22 Sep 2006 09:43:52 +0200
Message-ID: <1158911032.5473.94.camel@localhost.localdomain> (raw)
In-Reply-To: <450FEC1E.7080600@logix-tt.com>
References: <1158239339.5226.17.camel@localhost.localdomain>
	<450A75DE.6050102@logix-tt.com>
	<1158590646.5665.71.camel@localhost.localdomain>
	<450FBE15.9010905@logix-tt.com>
	<1158670101.5204.14.camel@localhost.localdomain>
	<450FEC1E.7080600@logix-tt.com>

Hi, Markus,

Le mardi 19 septembre 2006 à 15:09 +0200, Markus Schaber a écrit :
> Hi, Jerome,
> 
> Jérôme BENOIS wrote:
> 
> >>> Now i Have 335 concurrent connections, i decreased work_mem parameter to
> >>> 32768 and disabled Hyper Threading in BIOS. But my CPU load is still
> >>> very important.
> >> What are your settings for commit_siblings and commit_delay?
> > It default :
> > 
> > #commit_delay = 01   # range 0-100000, inmicroseconds
> > #commit_siblings = 5 # range 1-1000
> 
> You should uncomment them, and play with different settings. I'd try a
> commit_delay of 100, and commit_siblings of 5 to start with.
> 
> > I plan to return to previous version : 7.4.6 in and i will reinstall all
> > in a dedicated server in order to reproduce and solve the problem.
> 
> You should use at least 7.4.13 as it fixes some critical buts that were
> in 7.4.6. They use the same on-disk format and query planner logic, so
> they should not have any difference.
> 
> I don't have much more ideas what the problem could be.
> 
> Can you try to do some profiling (e. G. with statement logging) to see
> what specific statements are the one that cause high cpu load?
> 
> Are there other differences (besides the PostgreSQL version) between the
> two installations? (Kernel, libraries, other software...)
nothing.

I returned to the previous version 7.4.6 in my production server, it's
work fine !

And I plan to reproduce this problem in a dedicated server, and i will
send all informations in this list in the next week.

I hope your help for solve this problem.

Cheers,
Jérôme.

> HTH,
> Markus
-- 
Jérôme,

python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'sioneb@gnireenigne-aigra.rf'.split('@')])"

Attachments:

  signature.asc (application/pgp-signature, 190B) download

view thread (30+ messages)  latest in thread

Message-ID: <1158911032.5473.94.camel@localhost.localdomain>
Permalink:  ../1158911032.5473.94.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1158911032.5473.94.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: benois@argia-engineering.fr, schabi@logix-tt.com, milliard@argia.fr
  Subject: Re: High CPU Load
  In-Reply-To: <1158911032.5473.94.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox