i've been running some performance tests: the aim being to check how much slower JCL 1.1 runs that the 1.0.x releases. the figures for log4j are interesting. the raw data is below (the percentages are normalised to 1.0.4 benchmark times).
1. there is a small performance degradation between the 1.0.3, 1.0.4 and 1.1RC5 but not significant (a few percentiles). 2. 1.0.2 is a *lot* faster for log4j that the later releases 3. isDebugEnabled is a *lot* faster than logging 4. getLog is *slow* i have some ideas for improving performance against log4j (but testing them will have to wait till tomorrow). - robert RC5 GetLog: Duration=3943 3933 3928 3949 AVG 3938.25 ~106% Trace: Duration=1955 1961 1948 1960 AVG 1956 ~99% Debug: Duration=1954 1933 1945 1933 AVG 1941.25 ~99% isDebugEnabled: Duration=49 43 43 43 AVG 44.5 ~104% 1.0.4 GetLog: Duration=3715 3718 3711 3723 AVG 3716.75 100% Trace: Duration=1962 1947 1960 2000 AVG 1967.25 100% Debug: Duration=1953 1966 1952 1966 AVG 1959.25 100% isDebugEnabled: Duration=43 43 42 42 AVG 42.5 100% 1.0.3 GetLog: Duration=3667 3665 3671 3669 AVG 3668 ~99% Trace: Duration=1944 1944 1945 1944 AVG 1956.75 ~99% Debug: Duration=1946 1930 2096 1930 AVG 1975.5 ~101% isDebugEnabled: Duration=42 42 42 41 AVG 41.75 ~98% 1.0.2 GetLog: Duration=3588 3603 3590 3574 AVG 3588.75 ~97% Trace: Duration=65 52 52 52 AVG 55.25 3% Debug: Duration=45 46 46 46 AVG 45.75 2% isDebugEnabled: Duration=41 41 40 40 AVG 40.5 95% --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
