[
https://issues.apache.org/jira/browse/TIKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498178#comment-17498178
]
Manjunath Dhongadi commented on TIKA-3668:
------------------------------------------
yes, we have memory constraint of defined of about 1.5 GB.
<server>
<params>
<taskTimeoutMillis>3600000</taskTimeoutMillis>
<forkedJvmArgs>
<arg>-Xmx1536m</arg>
</forkedJvmArgs>
</params>
</server>
And one more thing, what we have observed is, when we explicitly disable
TesseractOCRParser the CPU utilisation is normal.
<parser-exclude class="org.apache.tika.parser.ocr.TesseractOCRParser"/>
> High CPU utilization in Tika 2.2.0
> ----------------------------------
>
> Key: TIKA-3668
> URL: https://issues.apache.org/jira/browse/TIKA-3668
> Project: Tika
> Issue Type: Bug
> Reporter: Manjunath Dhongadi
> Priority: Major
>
> Recently we upgraded Tika version from 1.26 to 2.2.0.
> We see the CPU utilization have gone high drastically(6 to 8 times more) in
> both cases Tesseract enabled and Tesseract disabled case.
> We are using tika-parsers-standard-package of 2.2.0.
> Whether this is normal behavior of high version of Tika 2.2.0.
> Any fine tuning parameters available for same.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
