3 ms·

I just tried the mentioned document in the viewer on http://mozilla.github.io/pdf.js/web/viewer.html http://mozilla.github.io/pdf.js/web/viewer.html I agree th

• acqq 12y ago
  Try to move through the pages, don't stay on the first one! I have the 22nm i7 CPU here and compared to the work with Adobe PDF reader it's just horrible having to use pdf.js. I must however admit that I'm not able to easily construct a Google search for more such documents, but I know a lot of people who work only with such -- they just can't work with pdf.js. Does your benchmark measure the time to actually display everything on every page (what the human looking at all the pages must do), or just the time until the browser is responsible? Edit: inspired from other comments, it seems that at least search for "math plots filetype:pdf" returns more guaranteed problems like http://www.engageny.org/sites/default/files/resource/attachments/math-g5-m4-lessons-1-12.pdf http://www.engageny.org/sites/default/files/resource/attachm... Still it's hard to find slow PDFs with certainty just by using Google.
  • bthorben 12y ago
    > Does your benchmark measure the time to actually display everything on every page (what the human looking at all the pages must do), or just the time until the browser is responsible? It "only" benchmarks the rendering, all the overhead the viewer produces is not shown. That is intentional, as we will create our own viewer anyway BTW: PDF.js in FF is typically slower than in Opera / Chrome, all these benchmarks used Opera