X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id AF8CCD1BA6C; Tue, 9 Mar 2004 20:29:51 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 48418-10; Tue, 9 Mar 2004 16:29:47 -0400 (AST) Received: from COLSWEEPER.cranel.com (newmail.cranel.com [66.192.200.227]) by svr1.postgresql.org (Postfix) with ESMTP id A7A47D1BAC8; Tue, 9 Mar 2004 16:29:44 -0400 (AST) Received: from colmail01.cranel.com (colmail01.cranel.com) by COLSWEEPER.cranel.com (Content Technologies SMTPRS 4.3.12) with ESMTP id ; Tue, 9 Mar 2004 15:29:01 -0500 Received: from cranel.com (gspiegelberg.cranel.com [192.168.11.134]) by colmail01.cranel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id GRDD7MRX; Tue, 9 Mar 2004 15:33:51 -0500 Message-ID: <404E2937.4060604@cranel.com> Date: Tue, 09 Mar 2004 15:29:43 -0500 From: Greg Spiegelberg Organization: Cranel, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: PgSQL Performance ML , Postgres Admin List Subject: syslog slowing the database? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/149 X-Sequence-Number: 12718 I've been waiting all day for a pg_restore to finish on a test system identically configured as our production in hardware and software with the exception prod is 7.3.5 and test is 7.4.1. The file it's restoring from is about 8GB uncompressed from a "pg_dump -b -F t" and after 2 hours the directory the database is in contains only 1GB. iostat reported ~2000 blocks written every 2 seconds to the DB file system. I turned syslog off to see if it was blocking anything and in the past couple minutes 1GB has been restored and iostat reports ~35,000 blocks written every 2 seconds to the DB file system. The system is completely idle except for this restore process. Could syslog the culprit? I turned syslog back on and the restore slowed down again. Turned it off and it sped right back up. Can anyone confirm this for me? Greg -- Greg Spiegelberg Sr. Product Development Engineer Cranel, Incorporated. Phone: 614.318.4314 Fax: 614.431.8388 Email: gspiegelberg@Cranel.com Cranel. Technology. Integrity. Focus.