[
https://issues.apache.org/jira/browse/TIKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486549#comment-17486549
]
Manjunath Dhongadi edited comment on TIKA-3668 at 2/3/22, 3:20 PM:
-------------------------------------------------------------------
"1) if our PDFParser is rendering pages for OCR even if Tesseract
is turned off, then that would cause this. I need to check if your header
request is actually working to turn off tesseract in the PDFParser."
Have verified this, Tesseract is not getting invoked, when flag
"X-Tika-OCRskipOcr: true" is passed as part of request.
2) If the forked process is restarting often, then that can peg a
machine. It looks like there's some warmup costs each time the forked process
is restarted. This can take ~a minute to come down to low levels of cpu usage.
If the forked process is restarting often, then that could peg a machine.
Need to verify about restart will check this by enabling loggers and come back.
We are using /tika /rmeta endpoints.
was (Author: JIRAUSER284592):
"1) if our PDFParser is rendering pages for OCR even if Tesseract
is turned off, then that would cause this. I need to check if your header
request is actually working to turn off tesseract in the PDFParser."
Have verified this, Tesseract is not getting invoked, when flag
"X-Tika-OCRskipOcr: true" is passed as part of request.
2) If the forked process is restarting often, then that can peg a
machine. It looks like there's some warmup costs each time the forked process
is restarted. This can take ~a minute to come down to low levels of cpu usage.
If the forked process is restarting often, then that could peg a machine.
Need to verify this by enabling loggers.
We are using /tika /rmeta endpoints.
> 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)
