From: Andre <pg@darix.de>
To: pgsql-performance@postgresql.org
Subject: Re: Server stalls, all CPU 100% system time
Date: Tue, 26 Feb 2013 22:53:17 +1000
Message-ID: <512CB03D.6080506@darix.de> (raw)
In-Reply-To: <15088.1361717159@sss.pgh.pa.us>
References: <512A1EC3.4020806@darix.de>
<15088.1361717159@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 25/02/2013 12:45 AM, Tom Lane wrote:
> 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
I used vmstat to look at the context swaps, they were around 5k and 15k interrupts per second.
I thought that it was to many interrupts and after a bit of search a website mentioned that the network card driver could cause that. After updating kernel and the driver the stalling is not reproducible any more.
Weird enough, when I load test the server now I have 35k interrupts and 250k context switches, but no problems at all.
Thanks for pointing me into the right direction.
--
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: pg@darix.de
Subject: Re: Server stalls, all CPU 100% system time
In-Reply-To: <512CB03D.6080506@darix.de>
* 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