Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 5D1221B31A53 for ; Thu, 24 May 2012 02:27:04 -0300 (ADT) Received: from corp.tradeindia.com ([61.16.154.82] helo=zmta01.trade-india-local.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SXQZi-0003U2-RF for pgsql-performance@postgresql.org; Thu, 24 May 2012 05:27:04 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by zmta01.trade-india-local.com (Postfix) with ESMTP id 0990F44E2863; Thu, 24 May 2012 10:56:48 +0530 (IST) X-Virus-Scanned: amavisd-new at zmta01.trade-india-local.com Received: from zmta01.trade-india-local.com ([127.0.0.1]) by localhost (zmta01.trade-india-local.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7Ma+t7rL9SC; Thu, 24 May 2012 10:56:47 +0530 (IST) Received: from zmbox01.trade-india-local.com (zmbox01.trade-india-local.com [192.168.1.111]) by zmta01.trade-india-local.com (Postfix) with ESMTP id B33E344E2B9E; Thu, 24 May 2012 10:56:47 +0530 (IST) Date: Thu, 24 May 2012 10:56:47 +0530 (IST) From: "Rajesh Kumar. Mallah" To: Claudio Freire Cc: pgsql-performance@postgresql.org Message-ID: <32382476.226771337837207313.JavaMail.root@zmbox01.trade-india-local.com> In-Reply-To: Subject: Re: High load average in 64-core server , no I/O wait and CPU is idle MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [192.168.1.114] X-Mailer: Zimbra 6.0.1_GA_1816.DEBIAN4.0 (ZimbraWebClient - FF3.0 (Linux)/6.0.1_GA_1816.DEBIAN4.0) X-Pg-Spam-Score: -0.5 (/) X-Archive-Number: 201205/116 X-Sequence-Number: 46940 ----- "Claudio Freire" wrote: | From: "Claudio Freire" | To: "Rajesh Kumar. Mallah" | Cc: pgsql-performance@postgresql.org | Sent: Thursday, May 24, 2012 9:23:43 AM | Subject: Re: [PERFORM] High load average in 64-core server , no I/O wait = and CPU is idle | | On Thu, May 24, 2012 at 12:39 AM, Rajesh Kumar. Mallah | wrote: | > The problem is that =C2=A0sometimes there are spikes of load avg which | > jumps to > 50 very rapidly ( ie from 0.5 to 50 =C2=A0within 10 secs) an= d | > it remains there for sometime and slowly reduces to normal value. | > | > During such times of high load average we observe that there is no | IO wait | > in system and even CPU is 50% idle. In any case the IO Wait always | remains < 1.0 % and | > is mostly 0. Hence the load is not due to high I/O wait which was | generally | > the case with our previous hardware. |=20 | Do you experience decreased query performance? Yes we do experience substantial application performance degradations. |=20 | Load can easily get to 64 (1 per core) without reaching its capacity. | So, unless you're experiencing decreased performance I wouldn't think | much of it. I far as i understand , Load Avg is the average number of processes waiting to be run in past 1 ,= =20 5 or 15 mins. A number > 1 would mean that countable number of processes were waiting to be run. how can load of more than 1 and upto 64 be OK for a 64 core machine ? |=20 | Do you have mcelog running? as a cron or a daemon? No we do not have mcelog. BTW the Postgresql version is : 9.1.3 which i forgot to mention=20 in my last email. regds mallah. | Sometimes, mcelog tends to crash in that way. We had to disable it in | our servers because it misbehaved like that. It only makes load avg | meaningless, no performance impact, but being unable to accurately | measure load is bad enough.