Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-performance-owner+M49339=pgsql-performance-ar@postgresql.org>)
	id 1UAK29-0007X4-F1 for pgsql-performance@arkaria.postgresql.org;
	Tue, 26 Feb 2013 12:53:25 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-performance-owner+M49339=pgsql-performance-ar@postgresql.org>)
	id 1UAK28-0008O8-RF for pgsql-performance@arkaria.postgresql.org;
	Tue, 26 Feb 2013 12:53:24 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <pg@darix.de>) id 1UAK27-0008O2-RO
	for pgsql-performance@postgresql.org; Tue, 26 Feb 2013 12:53:23 +0000
Received: from meyer-dlugosch.de ([81.169.140.174])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <pg@darix.de>) id 1UAK24-0000WQ-Km
	for pgsql-performance@postgresql.org; Tue, 26 Feb 2013 12:53:22 +0000
X-AuthUser: pg@darix.de
Received: from [192.168.0.3] ([127.0.0.1]:59165)
	by meyer-dlugosch.de with [XMail 1.24 ESMTP Server]
	id <SFFC181> for <pgsql-performance@postgresql.org> from <pg@darix.de>;
	Tue, 26 Feb 2013 14:13:34 +0100
Received: from [192.168.0.3] ([60.226.145.163] helo=[192.168.0.3]) by
	ASSP.nospam; 26 Feb 2013 14:13:33 +0100
Message-ID: <512CB03D.6080506@darix.de>
Date: Tue, 26 Feb 2013 22:53:17 +1000
From: Andre <pg@darix.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Server stalls, all CPU 100% system time
References: <512A1EC3.4020806@darix.de> <15088.1361717159@sss.pgh.pa.us>
In-Reply-To: <15088.1361717159@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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