[
https://issues.apache.org/jira/browse/PDFBOX-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018723#comment-14018723
]
Tilman Hausherr commented on PDFBOX-2117:
-----------------------------------------
There is another problem with this. PDFBOX-1915 also has a component "Review
and optimize the complete shading package for speed". This is a project that is
funded by google as part of the Google Summer of Code, and "my" student is
already working on the main parts (coons and tensor patches) and currently, she
is ahead of her plan, but I'd like her to keep her mind on these parts now. It
brings us into a potentially difficult situation, if there's nothing left to
optimize. I'm not criticizing you, nor telling you to stop, I'm just not sure
what to do. Maybe I will have to ask google.
Re the optimization: if the speed problem happens only due in the shading, why
not make this whole color lookup thing local to the shading?
> AxialShadingContext is slow
> ---------------------------
>
> Key: PDFBOX-2117
> URL: https://issues.apache.org/jira/browse/PDFBOX-2117
> Project: PDFBox
> Issue Type: Improvement
> Reporter: Petr Slaby
> Attachments: AxialShading.patch, Shading2Function2text.pdf,
> asy-shade.pdf, color_gradient.pdf, shading_pattern.pdf
>
>
> AxialShadingContext#getRaster() is on top of profiler hot spots in documents
> that use an axial shading. Inside it, the slowest part is calling
> PDColorSpaceRGB#toRGB() and PDFunctionType3#eval() (in this order).
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
