On Fri, 04 Nov 2005 09:35:31 -0800, Mark Womack wrote: > Do you have any actual timing or profiling information that would lead > you to suspect that log4j is causing the problem, or just anecdotal > experience? There is nothing I can think of that changed so much in any > of the recent log4j releases to account for the level of degradation you > are describing and have not seen it myself. > > If you switch back to version 1.2.9, does your problem go away?
Version 1.2.11 was our first version of log4j, prior to that we were generating much larger logs using (ServletContext).log(). Nobody has any numbers, it's just that log4j is new here and the people that probably should be fixing their previously existing performance problems are trying to blame it. -- Mac :}) Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
