You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tilman Hausherr (JIRA)" <ji...@apache.org> on 2015/11/06 16:23:27 UTC
[jira] [Issue Comment Deleted] (PDFBOX-3088) Cache glyph table to
optimize concurrent access
[ https://issues.apache.org/jira/browse/PDFBOX-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tilman Hausherr updated PDFBOX-3088:
------------------------------------
Comment: was deleted
(was: very weird. I'll investigate.)
> Cache glyph table to optimize concurrent access
> -----------------------------------------------
>
> Key: PDFBOX-3088
> URL: https://issues.apache.org/jira/browse/PDFBOX-3088
> Project: PDFBox
> Issue Type: Improvement
> Components: FontBox
> Affects Versions: 2.0.0
> Reporter: ccouturi
> Assignee: Tilman Hausherr
> Priority: Minor
> Labels: Optimization
> Fix For: 2.0.0
>
> Attachments: 0001-PDFBOX-3088-cache-glyph-table.patch, Benchmark.java, BenchmarkPDFBox3088.java, PDFBOX-3088.xlsx, test_medium.pdf
>
>
> If several threads convert several pdf to png (one thread access to a single document at a time) they are a contention on a lock in GlythTable. Jstack shows that all threads are in state blocked on the synchronized block in the getGlyph method. The lock is necessary, it's ok, but degrades performance.
> This patch cache glyphs already read.
> With the patch PDFBOX-3080, the follow benchmark compare 1000 pdf conversions with 1, 8, and 50 threads.
> || Simulation|| PDF 2.0-SNAPSHOT || With this patch + PDFBOX3080 ||
> || 1000 conversions / 1 thread | 120 s | 71 s|
> || 1000 conversions / 8 threads | 76 s | 28 s|
> || 1000 conversions / 50 threads | 81 s | 33 s|
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org