I don’t know. That is why I am asking if you guys have tried anything with Docker containers. Writing to stdout is a “best practice” so I am just trying to validate whether that is good or bad advice or what needs to be done to make it work well. Or if Log4j should implement a Docker plugin to write to, or something else.
> On Aug 6, 2018, at 8:28 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > Can't you just configure the console appender with a large-ish buffer and > remove the bottleneck? > > Gary > > On Mon, Aug 6, 2018 at 8:55 AM Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> So that begs the question, when logging to stdout in a container is a >> console attached? i.e. can you normally view the output like you could in a >> regular VM or is it all redirected somewhere else? I haven’t worked much >> with Docker yet so I am afraid I don’t know the answer. >> >> Ralph >> >>> On Aug 6, 2018, at 6:40 AM, Remko Popma <remko.po...@gmail.com> wrote: >>> >>> It may be to do with whether a tty is attached and how fast it is: >> https://stackoverflow.com/questions/3857052/why-is-printing-to-stdout-so-slow-can-it-be-sped-up >>> >>> (Shameless plug) Every java main() method deserves http://picocli.info >>> >>>> On Aug 6, 2018, at 4:21, Ralph Goers <ralph.go...@dslextreme.com> >> wrote: >>>> >>>> Our performance page shows that logging to the console is extremely >> slow. Yet one of the “best practices” for containers is to have the >> applications log to STDOUT or STDERR. This leads me to two questions: >>>> Is the performance of writing to STDOUT just as bad in a container? I >> have no reason to believe it wouldn’t be but have no evidence. >>>> Assuming performance is poor what are the realistic alternatives? Is >> there something more Log4j needs to be doing to play well in a cloud >> environment? >>>> >>>> Ralph >> >> >>
