[jira] [Updated] (LOG4J2-812) Performance optimization: avoid use of synchronized SimpleDateFormat in Dat​ePatternCo​nverter

[Remko Popma (JIRA)]

     [ 
https://issues.apache.org/jira/browse/LOG4J2-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Remko Popma updated LOG4J2-812:
-------------------------------
    Description: 
Threads seem to be blocking on class 
org.apache​.loggin.lo​g4j.core.p​attern.Dat​ePatternCo​nverter. It's short 
lived but is visible in profiler. It also is adding on to CPU. Here is the mail 
conversation on the mailing list:

{quote}
Ralph Goers ralph.go...@dslextreme.com via logging.apache.org  

The converter uses a SimpleDateFormat which is not thread safe and so is 
synchronized. I am sure there might be minor optimizations that could be done 
to this

 What I would do is modify DatePatternConverter to
 a) use Java 8’s java.time.format.DateTimeFormatter if running on Java 8
 b) use Joda Time’s DateTimeFormat if it is present.
 c) create a pool of SimpleDateFormat objects and use those.

 Please create a Jira issue for this.

 Ralph
{quote}
----

One alternative that  was suggested on the mailing list is to use commons lang 
FastDateFormat to format log timestamps.



  was:
Threads seem to be blocking on class 
org.apache​.loggin.lo​g4j.core.p​attern.Dat​ePatternCo​nverter. It's short 
lived but is visible in profiler. It also is adding on to CPU. Here is the mail 
conversation on the mailing list:

-------------


Ralph Goers ralph.go...@dslextreme.com via logging.apache.org  
 

4:28 PM (10 minutes ago)
 
 


 



to Log4J 

 
 







The converter uses a SimpleDateFormat which is not thread safe and so is 
synchronized. I am sure there might be minor optimizations that could be done 
to this

 What I would do is modify DatePatternConverter to
 a) use Java 8’s java.time.format.DateTimeFormatter if running on Java 8
 b) use Joda Time’s DateTimeFormat if it is present.
 c) create a pool of SimpleDateFormat objects and use those.

 Please create a Jira issue for this.

 Ralph


> Performance optimization: avoid use of synchronized SimpleDateFormat in 
> Dat​ePatternCo​nverter 
> -----------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-812
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-812
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>            Reporter: Mohit Anchlia
>            Assignee: Remko Popma
>
> Threads seem to be blocking on class 
> org.apache​.loggin.lo​g4j.core.p​attern.Dat​ePatternCo​nverter. It's short 
> lived but is visible in profiler. It also is adding on to CPU. Here is the 
> mail conversation on the mailing list:
> {quote}
> Ralph Goers ralph.go...@dslextreme.com via logging.apache.org  
> The converter uses a SimpleDateFormat which is not thread safe and so is 
> synchronized. I am sure there might be minor optimizations that could be done 
> to this
>  What I would do is modify DatePatternConverter to
>  a) use Java 8’s java.time.format.DateTimeFormatter if running on Java 8
>  b) use Joda Time’s DateTimeFormat if it is present.
>  c) create a pool of SimpleDateFormat objects and use those.
>  Please create a Jira issue for this.
>  Ralph
> {quote}
> ----
> One alternative that  was suggested on the mailing list is to use commons 
> lang FastDateFormat to format log timestamps.



--
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