Re: BUG #6650: CPU system time utilization rising few times a day

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: a(dot)krawiec(at)focustelecom(dot)pl
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6650: CPU system time utilization rising few times a day
Date: 2012-05-22 20:03:07
Message-ID: CA+TgmoaFJuJX0PSemmv+wVO73AY8yMrOts-3Ybt0i23A7fezkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 18, 2012 at 5:09 AM, <a(dot)krawiec(at)focustelecom(dot)pl> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      6650
> Logged by:          Andrzej Krawiec
> Email address:      a(dot)krawiec(at)focustelecom(dot)pl
> PostgreSQL version: 8.4.11
> Operating system:   CentOS 6.0 - 2.6.32-220.13.1.el6.x86_64
> Description:
>
> Primarily checked on PG 8.4.9 (same OS), problem also occurs. Few times a
> day I get a situation where PostgreSQL stops running for 1-2 minutes. CPU is
> running 99% in systime. IO is OK, only interrupts are extremely high (over
> 100k). System operates on 2 x Xeon 10 Core, 128 GB RAM, raid 10. Does anyone
> have any idea?

Try using strace to figure out where all that system time is going.
Sometimes the '-c' option is helpful.

It might also be helpful to connect gdb to the process and get a
backtrace, then continue, stop it again, get another backtrace.
Repeat that a few times and send us the backtrace that occurs most
frequently.

Is it a regular backend that is eating all that CPU time, or an
autovacuum worker?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2012-05-22 20:06:21 Re: BUG #6640: pg_dump does not always dump data of tables marked as editable in extension
Previous Message Robert Haas 2012-05-22 20:00:17 Re: BUG #6647: Password Issue