[pLog-svn] r847 - in plog/trunk/class: locale template/menu

Oscar Renalias oscar at renalias.net
Sun Jan 30 18:10:19 GMT 2005


I'm starting to be suspicious of log4php... The whole thing is just 
huge and each one of our objects (or any object which extends Object) 
inherits a $log object which is a pointer to a log4php logger. If you 
try to serialize one of these, you'll see what I mean by huge.

I'm thinking that we should get rid of it to see if it solves our 
problems. Memory-wise, we're not doing so many more things than in 
0.3.x so this could very well be the reason. We should either replace 
log4php with a smaller package providing similar functionality or 
implement our own logger. After all, we're using like 5% of log4php's 
power and it shouldn't be too difficult to implmement our own (which is 
the 2nd alternative) while keeping the same interface.

Any ideas?

Sorry to be so pushy, but would be good to have something to test 
during this week... (so that potential testers don't get too 
disappointed too early!)

Oscar

On 27 Jan 2005, at 03:32, Benjamin Krause wrote:

> Oscar Renalias wrote:
>
>> doing some memory profiling would be interesting but it could also
>> take a lot of time and I am not sure if there are any good tools for
>> doing this kind of things in php... It could be a pain to do this
>> manually!
>
> hey ...
>
> i've installed xdebug and did some profiling.. i'll investigate even 
> further the next days and send you a short report :)
>
> there are still a lot of possible warnings.. esp. in PHP5 .. xdebug 
> does
> a good job analysing the code ...
>
> http://www.xdebug.org/
>
> Ben
>
>




More information about the pLog-svn mailing list