Re: garbagefreeThreadContextMap default

Volkan Yazıcı <[email protected]>
Newsgroups gmane.comp.jakarta.log4j.user
Message-ID <CAP7pH7shZzrR6xwfm1tjsdAZOfAJL+YEzkaQLHiopJq7rWz2Ag@mail.gmail.com> 
There are various optimizations in Log4j depending on thread locals,
including garbage-free context map implementations. Thread locals are known
to not get along well with applications running a relatively high number of
threads. For one, servlet containers (Tomcat, JBoss, etc.) is a good
example of that. Further, as Remko remarked, garbage-free implementations
might perform worse – depending on the context, IMO.

On Wed, Aug 4, 2021 at 10:44 PM Joshua S <[email protected]> wrote:

> Why isn't garbagefreeThreadContextMap enabled by default?
>
> That is, does it have any disadvantages?
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.