Re: Adding more memory = hugh cpu load

From: alexandre - aldeia digital <adaldeia(at)gmail(dot)com>
To:
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Adding more memory = hugh cpu load
Date: 2011-10-11 11:54:42
Message-ID: 4E942E82.9010307@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Em 10-10-2011 23:19, Claudio Freire escreveu:
> On Tue, Oct 11, 2011 at 12:02 AM, Samuel Gendler
> <sgendler(at)ideasculptor(dot)com> wrote:
>> The original question doesn't actually say that performance has gone down,
>> only that cpu utilization has gone up. Presumably, with lots more RAM, it is
>> blocking on I/O a lot less, so it isn't necessarily surprising that CPU
>> utilization has gone up. The only problem would be if db performance has
>> gotten worse. Maybe I missed a message where that was covered? I don't see
>> it in the original query to the list.
>
> Load average (which is presumably the metric in question) includes
> both processes using the CPU and processes waiting for I/O.
> So it *would* be strange for load average to go up like that, if
> database configuration remains the same (ie: equal query plans)

Yep, that's the point. Iostat and vmstat reports a very low use of the
disks (lower than before the changes are made - perhaps because the cache).
Nothing changed in database itself.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message alexandre - aldeia digital 2011-10-11 12:14:50 Re: Adding more memory = hugh cpu load
Previous Message Ivan Voras 2011-10-11 10:20:45 Re: Adding more memory = hugh cpu load