You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2016/12/02 20:36:59 UTC
[jira] [Comment Edited] (TIKA-2180) Multiple requests on Tika to
extract text slows down
[ https://issues.apache.org/jira/browse/TIKA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716148#comment-15716148 ]
Tim Allison edited comment on TIKA-2180 at 12/2/16 8:36 PM:
------------------------------------------------------------
In short, I don't think there's much we can do to fix this. I think we've confirmed that this is not an issue with tika-server and that it is caused by our DOM-based docx parser.
Two points:
1) Try using the new (and experimental!) SAX docx parser that we just added in TIKA-1321. See [our wiki|https://wiki.apache.org/tika/MSOfficeParsers] for initial notes. Obviously, this only works with a fresh build from trunk at this point.
2) I'd want tika-batch to behave properly and shutdown after the given amount of time, but clearly the watchdog thread is getting starved by the GC. Perhaps the parent process should require a ping from the child process? If the GC is pegging the machine, though, and it apparently was even with only a single file processor, can we rely on the parent process not to be starved as well...
was (Author: tallison@mitre.org):
In short, I don't think there's much we can do to fix this. I think we've confirmed that this is not an issue with tika-server and that it is caused by our DOM-based docx parser.
Two points:
1) Try using the new (and experimental!) SAX docx parser that we just added in TIKA-1321. I'll try to add something on our wiki next week about it.
2) I'd want tika-batch to behave properly and shutdown after the given amount of time, but clearly the watchdog thread is getting starved by the GC. Perhaps the parent process should require a ping from the child process? If the GC is pegging the machine, though, and it apparently was even with only a single file processor, can we rely on the parent process not to be starved as well...
> Multiple requests on Tika to extract text slows down
> ----------------------------------------------------
>
> Key: TIKA-2180
> URL: https://issues.apache.org/jira/browse/TIKA-2180
> Project: Tika
> Issue Type: Bug
> Components: server
> Affects Versions: 1.13, 1.14
> Environment: Windows OS, Open JDK, 4 core 32 GB RAM
> Reporter: Ashish Basran
>
> I observed that if I send multiple requests to Tika (eg. http://localhost:8080/tika) with around 5MB files, Tika is very slow in completing the action. I tried with ~20 random files, it took 170 seconds to process all the files in sequence. If I pass all files in parallel, it took around 780 seconds to process same set of files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)