Re: Console performance

2018-04-02 Thread Remko Popma
Yes writing to the console on either Windows or Linux was ~50x(!) slower than writing to a file. This is documented on the log4j performance page. Mikael’s JIRA ticket on the direct option has some perf numbers: https://issues.apache.org/jira/browse/LOG4J2-1395 I seem to remember that the direc

Re: Console performance

2018-04-02 Thread Matt Sicker
>From what I remember, we didn't enable it by default because there's no official API docs about if it's supported by non-OpenJDK implementations. On 2 April 2018 at 12:28, Ralph Goers wrote: > They do it to allow Kubernetes to manage the configuration externally in a > generic way. Then it does

Re: Console performance

2018-04-02 Thread Ralph Goers
They do it to allow Kubernetes to manage the configuration externally in a generic way. Then it doesn’t matter if it is a Java app, Ruby, Python, C#, etc. They can use the same configuration on every container to do the same thing. What I am most interested in was the discussion we had some time

Re: Console performance

2018-04-02 Thread Chandra
In general, I believe writing stuff to stdout is a bad idea, even if you are just using it as a `debug` log.  the itchy thing for me is that there’s always another extra “piping” / “redirect” which has to happen for _persisting_ the log data. If you want to do that, why not just write it to a fi

Re: Console performance

2018-04-02 Thread Ralph Goers
The question is, what is the overhead when the console appender is redirected somewhere besides the console? Apparently the kubernetes configuration redirects stdout to somewhere else where it can be sent to Splunk or some other log aggregation tool. Raph > On Apr 2, 2018, at 10:08 AM, Matt Si

Re: Console performance

2018-04-02 Thread Matt Sicker
I always set direct="true" on console appenders (it's false by default because we added that option later). On 2 April 2018 at 12:05, Gary Gregory wrote: > I'm sure this is OS dependent as well. I've only seen the obvious: if you > log a ton of data, say at the DEBUG level, and enable DEBUG, the

Re: Console performance

2018-04-02 Thread Gary Gregory
I'm sure this is OS dependent as well. I've only seen the obvious: if you log a ton of data, say at the DEBUG level, and enable DEBUG, then yeah, things are going to slow down. Obvious. The complain I usually hear is that our server logs too much DEBUG data, and that users do not know which log ca

Console performance

2018-04-02 Thread Ralph Goers
Some of my team members at work are looking to move some services into Docker containers managed by Kubernetes following the guidance at https://12factor.net/logs . We have guidance that shows writing to the console is terrible and I remember having a discussion that