You may get better behavior with logstash logback encoder’s disruptive based appender, if performance is a concern.
> On May 22, 2021, at 12:32 PM, David Roussel <[email protected]> > wrote: > > It’s been many years since I read the code. But I seem to remember it’s > quite straight forward and just uses a java ArrayList, which will size itself > dynamically. But you’d best just read it yourself. > > IMHO the lock usage in the blocking queue isn’t great and could be more > efficient. But it does the job, and by not blocking on network IO it’s always > given me a good speed up. > > In the last project where is used logback I turned it on by default at the > begging of the project because it was such a clear win based on my past > experience. > > The default settings are fine. Setting a very high limit would only be > justified if you have a lot of memory and are expecting to have occasional > very slow periods of IO. > > But given you are writing to stdout, this will depend on the behaviour of the > log stream consumer abs how much buffering it does. > > I would expect any decent logging adapter to be built to cope with network > interruptions and buffer accordingly. > > Dave > _______________________________________________ > logback-user mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/logback-user _______________________________________________ logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
