From: Magnus Naeslund(t) <mag@fbab.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Spiegelberg <gspiegelberg@cranel.com>
Cc: PgSQL Performance ML <pgsql-performance@postgresql.org>
Cc: Postgres Admin List <pgsql-admin@postgresql.org>
Subject: Re: [PERFORM] syslog slowing the database?
Date: Wed, 10 Mar 2004 02:06:38 +0100
Message-ID: <404E6A1E.8040804@fbab.net> (raw)
In-Reply-To: <370.1078877805@sss.pgh.pa.us>
References: <404E2937.4060604@cranel.com>
<370.1078877805@sss.pgh.pa.us>
Tom Lane wrote:
> Greg Spiegelberg <gspiegelberg@cranel.com> 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
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: mag@fbab.net, tgl@sss.pgh.pa.us, gspiegelberg@cranel.com, pgsql-admin@postgresql.org
Subject: Re: [PERFORM] syslog slowing the database?
In-Reply-To: <404E6A1E.8040804@fbab.net>
* 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