Re: Log_file behavior in long running apps
| From: | Jon Parise | Date: | Fri, 04 Jul 2003 17:50:55 +0000 |
| Subject: | Re: Log_file behavior in long running apps | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-18006@lists.php.net to get a copy of this message | ||
On Fri, Jul 04, 2003 at 12:02:01PM +0200, Roman Neuhauser wrote:
> > > What effect will using Log::file in a long running application (non-web
> > > environment) have on memory usage given that it defers the writing till
> > > the end of the execution?
> >
> > I'm not sure. You'd have to run your own benchmarks.
>
> Well, I think we'll agree that it would cause evergrowing memory
> consupmtion.
>
> It also hampers functionality. Imagine any daemon like Apache only
> writing its logs on shutdown. You wouldn't be able to monitor its
> activity.
Sure. I believe the current Log_file class was designed for
short-lived web scripts, where the total output would be reasonable
and caching it is a performance win.
> > When I find the time to rewrite the Log_file class, I'll make the
> > output buffering optional.
>
> What are the other changes you want to make?
People have been asking for configurable timestamp and output formats.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)