Bug 89868 - pdftoppm takes about 2 hours at ~100% CPU to rasterize single-page PDF
Summary: pdftoppm takes about 2 hours at ~100% CPU to rasterize single-page PDF
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: utils (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-02 00:42 UTC by Yasin A.
Modified: 2018-08-21 10:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yasin A. 2015-04-02 00:42:51 UTC
On Ubuntu using Poppler 0.32.0

Rasterizing a single-page PDF at a 150 DPI resolution using pdftoppm takes about 7600 seconds at ~100%. The same PDF takes about 10 seconds to rasterize using Ghostscript.

I've run the following command for pdftoppm:

pdftoppm -cropbox -thinlinemode solid -r 150 -gray /path/to/slow.pdf /path/to/slow.ppm

And this one for gs:

gs -sDEVICE=tiffgray -sOutputFile=/path/to/slow.tiff -r150 -dBATCH -dNOPAUSE /path/to/slow.pdf

Since the PDF is sensitive, I'll need to send it via email to whomever is interested.

Any help would be appreciated. Thank you!
Comment 1 Albert Astals Cid 2015-04-03 12:51:46 UTC
I guess you can send it to me, but note i put non public files in the lowest of the stack of priority.
Comment 2 Yasin A. 2015-04-03 18:47:43 UTC
I've just sent the file.

As for the note on priority, that's perfectly understandable. Thanks for the heads-up though.
Comment 3 GitLab Migration User 2018-08-21 10:46:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/369.


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.