Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "LOG4J Developers Mailing List" <log4j-dev@jakarta.apache.org>
Message-Id: <5.0.2.1.0.20010813160651.01eb74a0@hoschek.mailbox.cern.ch>
Date: Mon, 13 Aug 2001 16:14:14 +0200
To: log4j-dev@jakarta.apache.org
From: Wolfgang Hoschek <wolfgang.hoschek@cern.ch>
Subject: Re: IO Buffering
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

Has there been any commit related to (optionally) using=20
BufferedOutputStream in File|Socket|SyslogAppender?
(and I don't mean AsyncAppender)

Wolfgang.

>Cool. Of course buffering means log4j should be shut down properly when
>exiting the JVM so as to flush the buffer. Here it would be highly
>useful to be able to depend on the 1.2 shutdown hook.
>
>Anders
>
>
>Ceki G=FClc=FC wrote:
> >
> > Anders,
> >
> > Do you remember the discussion we had about buffering in FileAppender?
> > We now have a real world example showing that you were right and I was=
=20
> wrong.
> > See  http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D2341
> >
> > My performance tests were done on my machine with a single user logged=
=20
> on, doing \
> > just the tests. In real world situation you have a many processes=20
> accessing the \
> > disk. And in that situation buffering is all the more important.
> > Fortunately, this one is not hard to fix. Cheers, Ceki
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org