[
https://issues.apache.org/jira/browse/TIKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107595#comment-18107595
]
Tim Allison commented on TIKA-4835:
-----------------------------------
On the regression corpus, the offenders in order:
* Image parsers requiring a file (49% of the extra tmp writing to disk)
* POIFSContainerDetector (~20%)
* ODF inline images, toFile() (~20%)
* DigestHelper (4%)
* PDFParser.scanXRefOffsets (5%)
> Diagnose performance issues in 4.0.0
> ------------------------------------
>
> Key: TIKA-4835
> URL: https://issues.apache.org/jira/browse/TIKA-4835
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> In both tika-server and tika-app, I'm seeing slower performance. This is
> somewhat explainable by the switch to pipes – we're trading robustness for
> speed.
> However, with some params on some docs on some vms, we're doing much better,
> and obv, tika-pipes in shared-server mode is much faster than the default
> isolated.
> I already opened a ticket to improve excess caching to disk, which wasn't
> great on a vm with a slowish drive. I also drafted this:
> https://tika.apache.org/docs/4.0.x/pipes/performance.html
> We should figure out if this is a change in how the parsers are working,
> something at the tika-level generally or something within pipes.
> There's more work to do here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
