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 DA650D1BA2E for ; Wed, 10 Mar 2004 01:06:42 +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 26034-03 for ; Tue, 9 Mar 2004 21:06:44 -0400 (AST) Received: from mail2.fbab.net (spectre.fbab.net [212.214.165.139]) by svr1.postgresql.org (Postfix) with SMTP id 7301CD1BA8F for ; Tue, 9 Mar 2004 21:06:39 -0400 (AST) Received: (qmail 26262 invoked by uid 136); 10 Mar 2004 01:06:42 -0000 Received: from mag@fbab.net by mail2.fbab.net by uid 133 with qmail-scanner-1.20rc1 (avp: 4.0.3.0. Clear:RC:0:. Processed in 0.053613 secs); 10 Mar 2004 01:06:42 -0000 Received: from unknown (HELO fbab.net) (magpool1@212.214.165.129) by mail2.fbab.net with SMTP; 10 Mar 2004 01:06:41 -0000 Message-ID: <404E6A1E.8040804@fbab.net> Date: Wed, 10 Mar 2004 02:06:38 +0100 From: "Magnus Naeslund(t)" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Greg Spiegelberg , PgSQL Performance ML , Postgres Admin List Subject: Re: [PERFORM] syslog slowing the database? References: <404E2937.4060604@cranel.com> <370.1078877805@sss.pgh.pa.us> In-Reply-To: <370.1078877805@sss.pgh.pa.us> 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/175 X-Sequence-Number: 12744 Tom Lane wrote: > Greg Spiegelberg writes: > >>I turned syslog back on and the restore slowed down again. Turned >>it off and it sped right back up. > > > We have heard reports before of syslog being quite slow. What platform > are you on exactly? Does Richard's suggestion of turning off syslog's > fsync help? > Another tip is to use a better (well atleast more optimized) syslog implementation, like metalog. It optimizes log writes to a blocksize that is better for disk throughput. You can also use "per line" mode with those if you want, i think. I use another logger that is called multilog (see at http://cr.yp.to), that's a pipe logger thing, like one per postmaster. It also gives very exact timestamps to every line, has built in log rotation and works nice with all programs i use it for. One thing is for sure, if you log much, standard syslog (atleast on linux) sucks big time. I gained back approx 30% CPU on a mailserver over here by changing to another logger. Cheers Magnus