If you're concerned about this, take a look at NLog, it's a younger, more active project. And development hasn't totally stopped, you can see in the svn repo that there's been some commits recently. Yes, it's kind of quiet, but maybe that's because it's a stable, mature project.I've never seen this behavior (and I've been using log4net since 1.1.1 (3 years) in high-traffic websites).I cut down logging to ~4GB/day, now the CPU usage is not noticeable at all. I had an app where I logged ~15GB/day and CPU usage was kind of high. Is anybody here having the same issues as me? So, I am considering giving up Log4Net in favor of the Microsoft Enterprise Library or something else. So, this starts to look as an abandoned open source project, and that usually means that it's time to move on to some alternative framework. Last but not least, I have not seen any new releases on the Apache website during the last three years. I've seem more than a few people online that complain on this and nobody seems to have a good solution. Rolling by date is often unreliable (it logs fine during the day, but then messes up the last day's log file around midnight). Some mission critical apps have to trace every step of every transaction. I would like to avoid the discussion of why so much tracing is needed. Some of my websites need to trace 5-10GB per day, and when I enable logging, the CPU utilization more than doubles. The CPU overhead with RollingFileAppendor is massive. So, wanted to see if anybody else has the same concerns: I've been using Log4Net on a few high traffic websites for a couple of years, and I cannot say that I am a happy customer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |