Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 7C0037591C6
	for <pgsql-performance@postgresql.org>;
	Thu, 24 May 2012 14:09:28 -0300 (ADT)
Received: from cl-174.chi-02.us.sixxs.net ([2001:4978:f:ad::2]
	helo=tamriel.snowman.net)
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <sfrost@tamriel.snowman.net>) id 1SXbXR-00051N-PH
	for pgsql-performance@postgresql.org; Thu, 24 May 2012 17:09:27 +0000
Received: by tamriel.snowman.net (Postfix, from userid 1000)
	id 05C0522940; Thu, 24 May 2012 13:09:12 -0400 (EDT)
Date: Thu, 24 May 2012 13:09:12 -0400
From: Stephen Frost <sfrost@snowman.net>
To: "Rajesh Kumar. Mallah" <mallah@tradeindia.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: High load average in 64-core server ,
  no I/O wait and CPU is idle
Message-ID: <20120524170912.GQ1267@tamriel.snowman.net>
References: <20120524155737.GP1267@tamriel.snowman.net>
	<8120287.465321337878795023.JavaMail.root@zmbox01.trade-india-local.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="7+eulfoxjVEk5kOS"
Content-Disposition: inline
In-Reply-To: 
 <8120287.465321337878795023.JavaMail.root@zmbox01.trade-india-local.com>
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/3.2.0-1-amd64 (x86_64)
X-Uptime: 13:08:12 up 87 days, 23:13, 14 users,  load average: 0.27, 0.13,
 0.07
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201205/127
X-Sequence-Number: 46951


--7+eulfoxjVEk5kOS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Rajesh Kumar. Mallah (mallah@tradeindia.com) wrote:
> We are running linux with kernel 3.2.X=20
> (which has the lseek improvements)

Ah, good.

> Thanks for the reference , even i thought so (LockManager) ,
> but we are actually also running out db max connections (also)=20
> ( which is currently at 600) , when that happens  something at=20
> the beginning of the application stack also gets dysfunctional and it=20
> changes the very input to the system. ( think of negative feedback system=
s )=20

Oh.  Yeah, have you considered pgbouncer?

> It is sort of complicated but i will definitely update list ,=20
> when i get to  the point of putting the blame on DB  :-) .

Ok. :)

	Thanks,

		Stephen

--7+eulfoxjVEk5kOS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk++azgACgkQrzgMPqB3kihOdgCfUSilCut+sGK0qw5/+6UWhOyd
IoEAn2JP9ux01J2RJql3JxHJeIIoWEQ9
=LMIW
-----END PGP SIGNATURE-----

--7+eulfoxjVEk5kOS--