| Summary: | better support for multicore platforms | ||
|---|---|---|---|
| Product: | poppler | Reporter: | Paul Millar <paul.millar> |
| Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Paul Millar
2012-06-12 00:29:34 UTC
Isn't this the same as Your just reported bug 50992? Hi Thomas, Again, thanks for the quick reply. My apologies if it's the same, but I don't believe so. In bug 50992, I'm asking that the API is thread-safe; that is, that multiple threads may call the poppler API without any potential corruption of any global state and, ideally, without contention between the different calling threads. This was the specific deficiency mentioned by the Okular developer when closing the ticket linked to in that bug. In this bug, I'm asking that a single API call uses as many cores as possible; that is, with a single rendering request, poppler makes best use of the available CPU cores. I believe that currently poppler is single threaded, so will use only a single core. Does that help explain the difference? Cheers, Paul -- 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/338. |
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.