[
https://issues.apache.org/jira/browse/LOG4J2-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-1680.
-------------------------------
Resolution: Fixed
Fixed in master.
Instead of creating a new Calendar object for each event, the current code
caches millisSinceMidnight and only instantiates a new Calendar if the current
time exceeds the midnightTomorrow boundary, effectively allocating one Calendar
object every 24 hours.
> (GC) Avoid allocating temporary objects in TimeFilter
> -----------------------------------------------------
>
> Key: LOG4J2-1680
> URL: https://issues.apache.org/jira/browse/LOG4J2-1680
> Project: Log4j 2
> Issue Type: Improvement
> Components: Filters
> Affects Versions: 2.7
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.8
>
>
> Make TimeFilter garbage-free or at least low-garbage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
