You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/11/27 20:59:00 UTC

[jira] [Commented] (TIKA-2511) Slowness parsing SQLite database file

    [ https://issues.apache.org/jira/browse/TIKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267529#comment-16267529 ] 

Hudson commented on TIKA-2511:
------------------------------

SUCCESS: Integrated in Jenkins build Tika-trunk #1398 (See [https://builds.apache.org/job/Tika-trunk/1398/])
TIKA-2511 Cache TikaConfig in EmbeddedDocumentUtil for faster processing (tallison: [https://github.com/apache/tika/commit/ce4d94888557a08f0535038e1586f235af0065b3])
* (edit) CHANGES.txt
* (edit) tika-core/src/main/java/org/apache/tika/extractor/EmbeddedDocumentUtil.java


> Slowness parsing SQLite database file
> -------------------------------------
>
>                 Key: TIKA-2511
>                 URL: https://issues.apache.org/jira/browse/TIKA-2511
>             Project: Tika
>          Issue Type: Bug
>    Affects Versions: 1.16
>            Reporter: Eamonn Saunders
>             Fix For: 1.17
>
>         Attachments: screenshot-1.png, urlclassifier3.sqlite
>
>
> Parsing of the attached urlclassifier3.sqlite database is approximately 5 times slower in Tika 1.16 than it was in 1.14.
> I've performed some profiling and it appears as though the problem lies in the number of times a new TikaConfig instance gets created. See attached screenshot
> I notice that EmbeddedDocumentUtil has 2 methods to get a TikaConfig, one of which caches the config instance. Are both methods needed? Why does EmbeddedDocumentUtil.getExtension() use the version that doesn't cache the config?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)