[
https://issues.apache.org/jira/browse/TIKA-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880546#comment-15880546
]
Hudson commented on TIKA-2276:
------------------------------
UNSTABLE: Integrated in Jenkins build tika-2.x #222 (See
[https://builds.apache.org/job/tika-2.x/222/])
TIKA-2276 -- pass through TikaConfig if not specified via ParseContext
(tallison: rev 4ebc441bd0da18a86d55eb4422cd76e3cc2b6288)
* (edit) tika-core/src/main/java/org/apache/tika/parser/AutoDetectParser.java
> Try to be more parsimonious creating TikaConfigs and ParseContexts
> ------------------------------------------------------------------
>
> Key: TIKA-2276
> URL: https://issues.apache.org/jira/browse/TIKA-2276
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Fix For: 2.0, 1.15
>
>
> If we run the AutoDetectParser() against the files in our unit tests (around
> 600 files*), there are 701 new instantiations of TikaConfig. The time is
> around 20 seconds. If we modify AutoDetectParser to pass its TikaConfig via
> the ParseContext if one isn't already specified, that drops to 234
> instantiations, and parse time goes to ~17 seconds.
> Let's make this simple change and look for other areas to decrease the number
> of times our parsers are creating a new TikaConfig.
> *Note I did not include the testCHM2.chm monster in these runs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
