1 Mar 2011 09:16
Updated: (JCR-2905) DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
Thomas Mueller (JIRA <jira <at> apache.org>
Updated: (JCR-2905) DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
2011-03-01 08:16:37 GMT
Updated: (JCR-2905) DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
2011-03-01 08:16:37 GMT
[
https://issues.apache.org/jira/browse/JCR-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-2905:
--------------------------------
Priority: Minor (was: Major)
Issue Type: Wish (was: Bug)
DateFormat.getDateTimeInstance() is only used if the log level is set to debug:
if (log.isDebugEnabled()) {
DateFormat df = DateFormat.getDateTimeInstance();
...
}
Do you really need to set the log level to debug?
Please note that DateFormat.format would need to be synchronized. Possibly a simpler solution would be:
new java.sql.Timestamp(timestamp.longValue()).toString()
However I'm not sure if this would work correctly (UTF versus local time zone).
> DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance
> ------------------------------------------------------------------------------------------
>
> Key: JCR-2905
> URL: https://issues.apache.org/jira/browse/JCR-2905
(Continue reading)
RSS Feed