X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 2F8C5D1B8AD for ; Thu, 28 Aug 2003 18:57:15 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 71080-07 for ; Thu, 28 Aug 2003 15:57:04 -0300 (ADT) Received: from harrier.cohaesio.com (harrier.cohaesio.com [212.97.128.50]) by svr1.postgresql.org (Postfix) with ESMTP id 97663D1B8CD for ; Thu, 28 Aug 2003 15:57:02 -0300 (ADT) Received: by harrier.cohaesio.com (Postfix, from userid 88) id 6607186; Thu, 28 Aug 2003 20:57:03 +0200 (CEST) X-Original-To: news2mail@news.cohaesio.com From: "Anders K. Pedersen" Subject: Re: Queries sometimes take 1000 times the normal time Date: Thu, 28 Aug 2003 20:57:02 +0200 Organization: Cohaesio A/S Lines: 27 Message-ID: References: <1062033258.71328.2.camel@jester> <1062095603.79027.205.camel@jester> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: harrier.cohaesio.com 1062097022 10377 212.97.128.160 (28 Aug 2003 18:57:02 GMT) X-Complaints-To: newsmaster@news.cohaesio.com X-Accept-Language: da, en-us, en To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/437 X-Sequence-Number: 3253 Rod Taylor wrote: >>With regards to other jobs on the server, there is a MySQL server on it >>as well, which from time to time has some multi-second queries generated >>from a webserver also on this host, but the MySQL is running with nice >>10 (PostgreSQL isn't nice'd). > > Do those MySQL queries hit disk hard? I guess they may be able to do so - the MySQL database is 450 MB, and the server has 512 MB RAM, and some of the queries pretty summarizes everything in the database. However, I just cross-referenced the access logs from the webserver with the duration logs, and although some of the spikes did happen, while there would have been some MySQL activity (I can't tell for sure, if it was simple queries or the long ones), other spikes happened without any website activity in the surrounding minutes. > I've never seen PostgreSQL have hicups like you describe when running on > a machine by itself. I have experienced similar issues when another > process (cron job in my case) caused brief swapping to occur. OK. I may have to try to put the database on a separate server. Regards, Anders K. Pedersen