You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/04/02 02:34:25 UTC
[jira] [Created] (LOG4J2-1349) Garbage-free ThreadContext map and
stack
Remko Popma created LOG4J2-1349:
-----------------------------------
Summary: Garbage-free ThreadContext map and stack
Key: LOG4J2-1349
URL: https://issues.apache.org/jira/browse/LOG4J2-1349
Project: Log4j 2
Issue Type: Improvement
Components: API
Affects Versions: 2.5
Reporter: Remko Popma
The current ThreadContext map and stack implementations allocate temporary objects. This ticket is to investigate and track the work for alternative implementations that are garbage-free.
Both DefaultThreadContextMap and DefaultThreadContextStack are copy-on-write data structures: each modification replaces the ThreadLocal object with a modified copy. The advantage of this approach is that there is no need to make a copy for each LogEvent.
Also, DefaultThreadContextMap uses a JDK map, the JDK collections tend to allocate a lot of temporary objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org