You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by pa...@apache.org on 2001/05/20 12:39:35 UTC
cvs commit: jakarta-log4j/src/xdocs index.xml
pathos 01/05/20 03:39:35
Modified: src/xdocs index.xml
Log:
Fixed typos and changed title to 'Introduction' (it used to be log4j project, but with the project.xml file also containing Log4j project, you got Log4j project - log4j project)
Revision Changes Path
1.3 +5 -5 jakarta-log4j/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 2001/01/18 07:49:40 1.2
+++ index.xml 2001/05/20 10:39:31 1.3
@@ -3,7 +3,7 @@
<properties>
<author email="cgu@apache.org">Ceki Gulcu</author>
- <title>log4j project</title>
+ <title>Introduction</title>
</properties>
<body>
@@ -17,7 +17,7 @@
<p>On the other hand, some people argue that log statements pollute
source code and decrease legibility. (We believe that the contrary is
-true). In the Java language where a pre-processor is not available,
+true). In the Java language where a preprocessor is not available,
log statements increase the size of the code and reduce its speed,
even when logging is turned off. Given that a reasonably sized
application may contain thousands of log statements, speed is of
@@ -47,9 +47,9 @@
log4j server, a remote Unix Syslog daemon or even a NT Event logger.</p>
<p>On a 233 MHz ThinkPad running JDK 1.1.7B, it costs about 46
-nano-seconds to determine if that statement should be logged or
-not. Actual logging is also quite fast, ranging from 79 micro-seconds
-using the SimpleLayout, 164 micro-seconds using the TTCCLayout and
+nanoseconds to determine if that statement should be logged or
+not. Actual logging is also quite fast, ranging from 79 microseconds
+using the SimpleLayout, 164 microseconds using the TTCCLayout and
around a millisecond when printing exceptions. The performance of the
PatternLayout is almost as good as the dedicated layouts, except that
it is a lot more flexible.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-cvs-help@jakarta.apache.org