After long work, I sent out the announcement for the first Log4PHP release this morning. Let’s see how this one works out – first reports from DBpedia users were promising. 
It’s an exciting time for all involved, and is the result of a culmination of many like-minded individuals. Everyone’s worked hard and as the initial test community seem to have responded positively and in such detail they could test anything from Word to Think Bingo (http://www.thinkbingo.com/) with their eyes closed. The people behind the development had a few words on the announcement of the first Log4PHP.
Here is the original statement:
The Log4PHP community is pleased to introduce the Apache Log4PHP 2.0.0 (Incubating) release [1]. It’s the first Log4PHP release since 2004 and tons of changes have been done. Finally Log4PHP has become a well tested framework made for PHP 5. Many thanks to all the contributors who made this release possible. Please download [2] Log4PHP and enjoy
The Log4PHP team
[1] http://incubator.apache.org/log4php/changes-report.html
[2] http://incubator.apache.org/log4php/download.html
Tags: Apache, Apache Log4PHP, PHP, Software
great great news!!
waiting for such a long time..
thanks.
Hello Christian,
I have a performance question about log4Php. I searched but couldn’t find too much info about performance.
I think log4php keeps the log file in memory, lets say you have 10000 visitor/day, keeping sql and some information logs cost too much?
Regards
Hi Serdar,
first I would like to point you to the users mailinglist for log4php were more people can share their expierences with you: its on the log4php site.
About your question: no, Log4PHP doesn’t hold logging events in memory. You can log to a file or to a database if you want to. For such an amount of users you are speaking, I would recommend to have only the most necessary statements logged. Most people are using error or warn level for production environments. This should only log few statements. But if you need such a heavy logging, you should consider logging to a database. Next question is: how much events do you create? Assuming 10000 visitors requesting 10 pages = 100.000 requests. If you create only 10 logging events you can expect 1.000.000 sql statements to be executed. Is your database ready for this?
If not, I recommend you to have excessive logging on debug level only on test environment, for production only log on error level. This should result in few occasions.
Hope that helped you a bit – hope to see you on the mailinglist. Maybe with some of your experiences
Best
Christian
Hello Christian,
thanks for response, it helped a lot.
I subscribed to mailing list and of course I am gonna share my experience.
I used log4Net for a while and as I know, log4Net keeps the file in memory so I assume the same for log4Php.
I am using files and emails for Fatal level errors.
I just wanted to give an example by saying 10000, but you are right 1 million log is not good idea. The best thing would be keeping critical logs such as delete etc.
Thank you for all info