[logback-dev] [JIRA] (LOGBACK-1422) Deadlock with logging

QOS.CH (JIRA) Tue, 29 Oct 2019 08:14:10 -0700

Title: Message Title

Ralph Goers commented on

I just want to add my 2 cents here. I know that the guidelines for [12 factor apps|https://12factor.net/] say to log to the console. As I documented at [Logging in the Cloud|http://logging.apache.org/log4j/2.x/manual/cloud.html] if you have significant logging or performance is a concern logging to the standard output stream, and especially the console, is a bad idea as the performance is much slower. I would encourage you to run this [benchmark|https://github.com/apache/logging-log4j2/blob/release-2.x/log4j-perf/src/main/java/org/apache/logging/log4j/perf/jmh/OutputBenchmark.java] on your system to show how poor it is. On my system I got the following results where "console" is writing to the console, "redirect" is the standard output stream redirected to a file (which is essentially what Docker does), and lastly writing to the file directly. You can see there is a huge difference.

 
                                                                Benchmark                  Mode  Cnt       Score       Error  Units
OutputBenchmark.console   thrpt   20   39291.885 ±  3370.066  ops/s
OutputBenchmark.file      thrpt   20  654584.309 ± 59399.092  ops/s
OutputBenchmark.redirect  thrpt   20   70284.576 ±  7452.167  ops/s 
                                                            

Add Comment

This message was sent by Atlassian JIRA

_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev

[logback-dev] [JIRA] (LOGBACK-1422) Deadlock with logging

Reply via email to