Certain PDFs opened in Evince or Atril using the Poppler backend are extremely slow to render, to the point of being unusable. This is on a very fast Thinkpad laptop with a quad-core processor and an SSD. The same PDFs render instantly using a Windows PDF reader (http://www.tracker-software.com/product/pdf-xchange-viewer) (running under Wine!!).
This file is only about 2MB, but it takes many seconds to render each page:
On the other hand, some long, complex PDFs with images render quickly with Poppler, like this one:
Thanks for looking into this.
Reference bug #91248
It renders around the second mark here both in Splash and Cairo.
Not specially slow.
i7-2670QM CPU @ 2.20GHz
Hmm strange, for me it's over 5 seconds to render the first page, and then almost 3 seconds to render page 20 when I jump to it.
Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Did you compile poppler yourself? What are you using to measure the times? Use ./qt4/tests/test-poppler-qt4 or ./glib/demo/poppler-glib-demo from the compile tree.
Hi there, I'm just using the regular Ubuntu 15.04 binaries of Poppler 0.30.0. I used a stopwatch to time it from opening the page until the spinner goes away and I can read the page.
Then you're not meausing the time takes to render the file, you're measuring the time evince takes to put it into screen, there's lots of layers in the middle that can be the culprit.
Well, the end user doesn't care about the layers in between. All the user knows is that the PDF reader is unusably slow. I'm happy to run any other tests, with instructions if possible.
The end user should file a bug against evince then if the end user is not sure poppler is the culprit.
rendering is slow "1.2s" per page, plus getting page info 1s, so in evince you get a around 2second rendering time. so, of course there are things en evince that we could do, but ptrobably therare also things in poppler we could do, but I agree with albert t hat 1.2 seconds is not super slow!.
When you refer to "rendering time" are you talking about the time it takes Poppler to do its work, or the time that it takes for the image to appear on the screen for the end user?
Yes, when saying 2s of perceived rendering time it's the time you see in evince. This is because in evince we do several things, and we don't make parallel calls to poppler, so you have to wait for both processes to finish.
I see. So why is Evince/Atril taking 3 - 5 seconds to show me each page, despite my fast system?
I really do appreciate you guys looking into this, I pretty much live in a PDF viewer, and this performance issue is killing me.
S., you opened a bug in evince for this file as well, please comment things related to evince to the evince bug not here. Here we only comment about the strict rendering period of poppler, which as far as I can see is related to color correction using lcms.
-- 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/507.