[
https://issues.apache.org/jira/browse/TIKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210247#comment-13210247
]
Andrzej Bialecki commented on TIKA-864:
----------------------------------------
I noticed this issue when profiling a larger application that uses a
configurable pool of threads (hundreds) to process the Enron data-set (the
version in plain text RFC822 format, available here
http://www.cs.cmu.edu/~enron/enron_mail_20110402.tgz). I didn't measure in
numbers the impact of this particular method call on the whole process, but I
saw that threads were very often blocked on a few sync blocks, among others on
this one and the one in TIKA-865.
> Metadata.formatDate should use ThreadLocal
> ------------------------------------------
>
> Key: TIKA-864
> URL: https://issues.apache.org/jira/browse/TIKA-864
> Project: Tika
> Issue Type: Improvement
> Components: metadata
> Reporter: Andrzej Bialecki
>
> Currently this is a synchronized method that uses a single instance of
> DateFormat. Instead it could use a pool of ThreadLocal DateFormat instances
> and avoid the sync blocking.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
