X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 6D2239FB37C for ; Fri, 22 Sep 2006 04:44:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 22426-03 for ; Fri, 22 Sep 2006 07:43:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp-msa-out19.orange.fr (smtp19.orange.fr [80.12.242.1]) by postgresql.org (Postfix) with ESMTP id 6E2BE9FB397 for ; Fri, 22 Sep 2006 04:43:58 -0300 (ADT) Received: from [192.168.1.192] (LSt-Amand-152-32-6-178.w82-127.abo.wanadoo.fr [82.127.21.178]) by mwinf1903.orange.fr (SMTP Server) with ESMTP id 6A9E91C000B6; Fri, 22 Sep 2006 09:43:55 +0200 (CEST) X-ME-UUID: 20060922074355436.6A9E91C000B6@mwinf1903.orange.fr Subject: Re: High CPU Load From: =?ISO-8859-1?Q?J=E9r=F4me?= BENOIS To: Markus Schaber Cc: pgsql-performance@postgresql.org, Xavier Milliard 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> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-fkpH5K3xiDkvoRArD6mQ" Date: Fri, 22 Sep 2006 09:43:52 +0200 Message-Id: <1158911032.5473.94.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/295 X-Sequence-Number: 20981 --=-fkpH5K3xiDkvoRArD6mQ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Markus, Le mardi 19 septembre 2006 =C3=A0 15:09 +0200, Markus Schaber a =C3=A9crit = : > Hi, Jerome, >=20 > J=C3=A9r=C3=B4me BENOIS wrote: >=20 > >>> 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 : > >=20 > > #commit_delay =3D 01 # range 0-100000, inmicroseconds > > #commit_siblings =3D 5 # range 1-1000 >=20 > 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. >=20 > > I plan to return to previous version : 7.4.6 in and i will reinstall al= l > > in a dedicated server in order to reproduce and solve the problem. >=20 > 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. >=20 > I don't have much more ideas what the problem could be. >=20 > 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? >=20 > 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=C3=A9r=C3=B4me. > HTH, > Markus --=20 J=C3=A9r=C3=B4me, python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for p in 'sioneb@gnireenigne-aigra.rf'.split('@')])" --=-fkpH5K3xiDkvoRArD6mQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBFE5Q4CDKlmlhpwnERAiE0AJ9y+hicTdzUMa5NpSFKAteaabVc6gCeOIdW Sa1FwshA0up+oKIS2Q4RKTM= =Ftfl -----END PGP SIGNATURE----- --=-fkpH5K3xiDkvoRArD6mQ--