From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andre <pg@darix.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Server stalls, all CPU 100% system time
Date: Sun, 24 Feb 2013 09:45:59 -0500
Message-ID: <15088.1361717159@sss.pgh.pa.us> (raw)
In-Reply-To: <512A1EC3.4020806@darix.de>
References: <512A1EC3.4020806@darix.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Andre <pg@darix.de> writes:
> Since our upgrade of hardware, OS and Postgres we experience server stalls under certain conditions, during that time (up to 2 minutes) all CPUs show 100% system time. All Postgres processes show BIND in top.
Odd. I wonder if you are seeing some variant of the old context swap
storm problem. The "99.8% system time" reading is suggestive but hardly
conclusive. Does top's report of context swap rate go to the moon?
It would be interesting to strace a few of the server processes while
one of these events is happening, too.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, pg@darix.de
Subject: Re: Server stalls, all CPU 100% system time
In-Reply-To: <15088.1361717159@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox