Claudio Freire wrote:
> Stephen Frost wrote:
>> Rajesh Kumar. Mallah (mal...@tradeindia.com) wrote:
>>> we are actually also running out db max connections (also)
>>> ( which is currently at 600) , when that happens something at
>>> the beginning of the application stack also gets dysfunctional
On Thu, May 24, 2012 at 2:09 PM, Stephen Frost wrote:
> * Rajesh Kumar. Mallah (mal...@tradeindia.com) wrote:
>> We are running linux with kernel 3.2.X
>> (which has the lseek improvements)
>
> Ah, good.
>
>> Thanks for the reference , even i thought so (LockManager) ,
>> but we are actually also
* Rajesh Kumar. Mallah (mal...@tradeindia.com) wrote:
> We are running linux with kernel 3.2.X
> (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)
> ( which is currently at
- "Stephen Frost" wrote:
| From: "Stephen Frost"
| To: "Rajesh Kumar. Mallah"
| Cc: pgsql-performance@postgresql.org
| Sent: Thursday, May 24, 2012 9:27:37 PM
| Subject: Re: [PERFORM] High load average in 64-core server , no I/O wait and
CPU is idle
|
| From: "Steve Crawford"
| To: "Rajesh Kumar. Mallah"
| Cc: "Andy Colson" , "Claudio Freire"
, pgsql-performance@postgresql.org
| Sent: Thursday, May 24, 2012 9:23:47 PM
| Subject: Re: [PERFORM] High load average in 64-core server , no I/O wait and
Rajesh,
* Rajesh Kumar. Mallah (mal...@tradeindia.com) wrote:
> We are puzzled why the CPU and DISK I/O system are not being utilized
> fully and would seek lists' wisdom on that.
What OS is this? What kernel version?
> just a thought, will it be a good idea to partition the host hardware
>
On 05/24/2012 05:58 AM, Rajesh Kumar. Mallah wrote:
Dear Andy ,
Following the discussion on load average we are now investigating on some
other parts of the stack (other than db).
Essentially we are bumping up the limits (on appserver) so that more requests
goes to the DB server.
Which leads
Dear Andy ,
Following the discussion on load average we are now investigating on some
other parts of the stack (other than db).
Essentially we are bumping up the limits (on appserver) so that more requests
goes to the DB server.
|
| Maybe you are hitting some locks? If its not IO and no
On 05/24/2012 12:26 AM, Rajesh Kumar. Mallah wrote:
- "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 i
|
| Load avg is the number of processes in the running queue, which can
| be either waiting to be run or actually running.
|
| So if you had 100% CPU usage, then you'd most definitely have a load
| avg of 64, which is neither good or bad. It may simply mean that
| you're using your hardware's ful
On Thu, May 24, 2012 at 2:26 AM, Rajesh Kumar. Mallah
wrote:
> |
> | 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 proce
- "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
On Thu, May 24, 2012 at 12:39 AM, Rajesh Kumar. Mallah
wrote:
> The problem is that sometimes there are spikes of load avg which
> jumps to > 50 very rapidly ( ie from 0.5 to 50 within 10 secs) and
> it remains there for sometime and slowly reduces to normal value.
>
> During such times of high
Dear List ,
We are having scalability issues with a high end hardware
The hardware is
CPU = 4 * opteron 6272 with 16 cores ie Total = 64 cores.
RAM = 128 GB DDR3
Disk = High performance RAID10 with lots of 15K spindles and a working BBU
Cache.
normally the 1 min load average of the system
14 matches
Mail list logo