Hello Vlad,
Quoting [1],
This tests are done using log4j version 1.2.9, and java version: 1.4.2_05.
Have you looked at the latest code in the log4j CVS repository? See in particular
the new org.apache.log4j.spi.location package [2]. We now use the same technique
as your Java14LocationInfo with the same improvement results.
In your conclusion, you state:
"It would be nice to extend next version for log4j 1.3.0 with support for java 1.4. Or allow to customize LocationInfo class."
But that is exactly what we have done! :-)
Your conclusions about the sluggishness of transporting LoggingEvent objects over the wire is well taken. One way of achieving better performance consists of having the LoggingEvent class take over its own serialization. This leads to about 10 fold increase in performance. However, this comes at the cost of losing serialization time compatibility between previous versions of log4j and version 1.3.
I wonder how we can better coordinate our efforts to avoid duplicating our mutual efforts.
By the way, you've made my day.
[1] http://jour.sourceforge.net/log4j_LocationInfo_performance.html
[2] http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/log4j/spi/location/
or its tinyURL equivalent http://tinyurl.com/5gjdy
At 05:09 AM 11/24/2004, Vlad Skarzhevskyy wrote:
Hello log4j developers.
I have spent some time measuring speed of class org.apache.log4j.spi.LocationInfo.
[cut]
-- Vlad
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
