Still using log4j? Use log4j2 quickly, the performance is too fierce!

Java technology stack 2021-09-15 10:37:47

Environmental Science

jdk:1.7.0_79

cpu:i5-4570@3.20GHz 4 nucleus

eclipse:3.7

operating system :win7

Get ready

1.log4j:1.7.21

<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.7.21</version>
</dependency>

log4j.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
<appender name="myConsole" class="org.apache.log4j.ConsoleAppender">
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%d{dd HH:mm:ss,SSS\} %-5p] [%t] %c{2\} - %m%n" />
</layout>
<!-- The filter sets the level of output -->
<filter class="org.apache.log4j.varia.LevelRangeFilter">
<param name="levelMin" value="debug" />
<param name="levelMax" value="warn" />
<param name="AcceptOnMatch" value="true" />
</filter>
</appender>
<appender name="myFile" class="org.apache.log4j.DailyRollingFileAppender">
<param name="File" value="log4jTest.log" />
<param name="Append" value="true" />
<param name="DatePattern" value="'.'yyyy-MM-dd'.log'" />
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="[%t] - %m%n" />
</layout>
</appender>
<appender name="async_file" class="org.apache.log4j.AsyncAppender">
<param name="BufferSize" value="32" />
<appender-ref ref="myFile" />
</appender>
<logger name="org.logTest" additivity="false">
<level value="info" />
<appender-ref ref="async_file" /> <!-- Sync :FILE asynchronous :async_file -->
</logger>
</log4j:configuration>

2.logback:1.1.7

<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.1.7</version>
</dependency>

logback.xml

<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<!-- encoder Default configuration is PatternLayoutEncoder -->
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n
</pattern>
</encoder>
</appender>
<appender name="FILE" class="ch.qos.logback.core.FileAppender">
<file>testFile.log</file>
<append>true</append>
<encoder>
<pattern>[%t] - %m%n
</pattern>
</encoder>
</appender>
<!-- Asynchronous output -->
<appender name="ASYNC" class="ch.qos.logback.classic.AsyncAppender">
<discardingThreshold>0</discardingThreshold>
<appender-ref ref="FILE" />
</appender>
<logger name="org.logTest" level="INFO"
additivity="false">
<appender-ref ref="ASYNC" /> <!-- Sync :FILE asynchronous :ASYNC-->
</logger>
<root level="ERROR">
<appender-ref ref="STDOUT" />
</root>
</configuration>

3.log4j2:2.6.2

<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.6.2</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>2.6.2</version>
</dependency>
<dependency>
<groupId>com.lmax</groupId>
<artifactId>disruptor</artifactId>
<version>3.3.4</version>
</dependency>

log4j2.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- Set up log4j2 Of itself log The level of warn -->
<configuration status="warn">
<appenders>
<console name="Console" target="SYSTEM_OUT">
<PatternLayout pattern="[%d{HH:mm:ss:SSS}] [%p] - %l - %m%n" />
</console>
<RollingFile name="RollingFileInfo" fileName="info.log"
filePattern="${sys:user.home}/logs/hpaasvc/$${date:yyyy-MM}/info-%d{yyyy-MM-dd}-%i.log">
<Filters>
<ThresholdFilter level="INFO" />
<ThresholdFilter level="WARN" onMatch="DENY"
onMismatch="NEUTRAL" />
</Filters>
<PatternLayout pattern="[%t] - %m%n" />
<Policies>
<TimeBasedTriggeringPolicy />
<SizeBasedTriggeringPolicy size="100 MB" />
</Policies>
</RollingFile>
<RandomAccessFile name="RandomAccessFile" fileName="asyncWithLocation.log"
immediateFlush="false" append="true">
<PatternLayout>
<Pattern>[%t] - %m%n</Pattern>
</PatternLayout>
</RandomAccessFile>
</appenders>
<loggers>
<!-- <AsyncLogger name="asynLogger" level="trace"
includeLocation="true">
<AppenderRef ref="RandomAccessFile" />
</AsyncLogger> -->
<Root level="info" includeLocation="true">
<AppenderRef ref="RollingFileInfo" />
</Root>
</loggers>
</configuration>

test

Get ready 50 All threads record at the same time 1000000 Data , Then count the time , The detailed code is as follows :

import java.util.concurrent.CountDownLatch;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public class App {
private static Logger log = LoggerFactory.getLogger(App.class);
public static void main(String[] args) throws InterruptedException {
int messageSize = 1000000;
int threadSize = 50;
final int everySize = messageSize / threadSize;
final CountDownLatch cdl = new CountDownLatch(threadSize);
long startTime = System.currentTimeMillis();
for (int ts = 0; ts < threadSize; ts++) {
new Thread(new Runnable() {
@Override
public void run() {
for (int es = 0; es < everySize; es++) {
log.info("======info");
}
cdl.countDown();
}
}).start();
}
cdl.await();
long endTime = System.currentTimeMillis();
System.out.println("log4j1:messageSize = " + messageSize
+ ",threadSize = " + threadSize + ",costTime = "
+ (endTime - startTime) + "ms");
}
}

log4j1 and logback The synchronization and asynchrony of are modified to the corresponding appender That's it

log4j2 The asynchronous mode of provides 2 Middle mode :

1. Global on

Set up Log4jContextSelector The system attribute is :
org.apache.logging.log4j.core.async.AsyncLoggerContextSelector

System.setProperty("Log4jContextSelector", "org.apache.logging.log4j.core.async.AsyncLoggerContextSelector");

2. Mixed synchronous asynchronous mode

You don't have to set it Log4jContextSelector, But it needs to be used AsyncLogger label

Refer to the official documentation for more details :http://logging.apache.org/log4j/2.x/manual/async.html#AllAsync

result
After each test, the statistics are as follows :

log4j2 The asynchronous mode of shows an absolute performance advantage , The advantage is mainly due to Disruptor Use of framework

LMAX Disruptor technology. Asynchronous Loggers internally use the Disruptor, a lock-free inter-thread communication library, instead of queues, resulting in higher throughput and lower latency.

A lockless inter thread communication library replaces the original queue

more Disruptor :

http://developer.51cto.com/art/201306/399370.htm

http://ifeve.com/disruptor/

source :https://my.oschina.net/OutOfMemory/blog/789267

Recent hot article recommends :

1.1,000+ Avenue Java Arrangement of interview questions and answers (2021 The latest version )

2. Don't fill the screen again if/ else 了 , Try strategy mode , It's delicious !!

3. Oh my god !Java Medium xx ≠ null What is the new grammar ?

4.Spring Boot 2.5 Blockbuster released , Dark mode is too explosive !

5.《Java Development Manual ( Song Mountain version )》 The latest release , Download it quickly !

I think it's good , Don't forget to like it + Forward !

Please bring the original link to reprint ,thank
Similar articles

2021-09-15

2021-09-15