From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrzej Krawiec <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-23 18:01:51 |
Message-ID: | CA+TgmobnWsDfFdNW-APy_D4Y-taX=zu1RUyT4hM5xkKV1_UZag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, May 23, 2012 at 5:29 AM, Andrzej Krawiec
<a(dot)krawiec(at)focustelecom(dot)pl> wrote:
> Cannot strace or gdb on a production system under heavy load (about 100
> transactions per second).
> It's in kernel space not user, so we are unable to anything at this
> particular moment (sometimes even the ssh connection seems to hang for a
> while).
> We suspect neither autovacuum (although suspected primarily) nor regular
> backend. It is system time. The question is: what's the reasone for that?
> We've dug through system and postgres logs, cleared out most of the long
> query problems, idle in transaction, optimized queries, vacuumed, reindexed
> and such.
> For a while it seemed like the particular kernel version is causing majority
> of problems. We have downgraded to 2.6.32.-71.29.1.el6.x86_64 and those
> problems went mostly! away. For few days we had no situations, but it
> happened again.
perf can tell you about problems in kernel-space, but I'm not sure it
exists that far back.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-05-24 00:33:02 | Re: PostgreSQL 9.2 beta1's pg_upgrade fails on Windows XP |
Previous Message | Chaitany Kulkarni | 2012-05-23 17:42:06 | Re: BUG #6660: losing schema name in pg_dump |