[
https://issues.apache.org/jira/browse/PDFBOX-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384441#comment-15384441
]
Tilman Hausherr commented on PDFBOX-3429:
-----------------------------------------
I realize my text from this morning wasn't really helpful - the classic
profiler can find CPU or memory load but not excessive locking. I don't have a
solution for that one, sadly. The google keywords are: java profiler lock
contention. But I didn't find anything that would output what I really want,
i.e. stack trace pairs.
> Improve ExtractText Concurrency
> -------------------------------
>
> Key: PDFBOX-3429
> URL: https://issues.apache.org/jira/browse/PDFBOX-3429
> Project: PDFBox
> Issue Type: Improvement
> Components: Text extraction
> Affects Versions: 2.0.1
> Environment: Win7, jdk1.8.0_60 x64
> Reporter: Luis Filipe Nassif
> Priority: Minor
> Labels: optimization
> Attachments: cpu-pdfbox-2.0.1.png, cpu-pdfbox1.8.10.png
>
>
> While testing Tika 1.13, which uses PDFBox 2.0.1, from a multithreaded text
> extraction application, I noted cpu usage aroung 80% in my 6 core computer
> when processing a dataset of ~75 thousands of pdfs (18GB). It took 5min25sec
> to complete the text extraction. With Tika 1.10, which uses PDFBox 1.8.10,
> cpu usage stays aroung 100%. It took 4min37sec to complete. The dataset is
> read from a ramdrive, so there is no i/o bottleneck. I suspect there is some
> new synchronization code that blocks the threads for a non trivial amount of
> time, resulting in less cpu usage than before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
