Summary: | splash patch to make pdftops 5% faster on some images | ||
---|---|---|---|
Product: | poppler | Reporter: | William Bader <williambader> |
Component: | splash backend | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | williambader |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | splash patch to make pdftops 5% faster on some images |
Description
William Bader
2011-02-07 12:58:23 UTC
I'm not really convinced about the first part, you are "inlininig" only one of the 11 uses of pipeRun? >I'm not really convinced about the first part, you are "inlininig" only one of
the 11 uses of pipeRun?
Thanks for looking at it.
I inlined two specific options of one place that lead to the most calls to pipeRun() in some of my test files that took the longest for pdftops to process. I built pdftops with profiling and traced the locations of the calls. It eliminated about half of the calls to pipeRun(). The remaining calls were from other locations or with options that would have required inlining the full logic of pipeRun().
William
That might work for you but sincerely i don't see it happening in us only changing only 1 out of the 11 because it helped in some pdf files. If you want something like this to be commited you have to find a way to "optimize" them all without the code becoming a mess. >That might work for you but sincerely i don't see it happening in us
OK. Can you take just the second part?
Do you want me to submit a new patch file?
William
2nd part Commited to master Thanks! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.