bthorben

6 ms·

1. 1.▲
   by 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 t
2. 2.▲
   by bthorben 12y ago

   MuPDF is a very nice piece of software, but it's GPL licensed. As I understand it, this basically prevents MuPDF from actually being used in commercial software ... unless of course we would make the software open source ...
3. 3.▲
   by bthorben 12y ago

   I just tried the mentioned document in the viewer on http://mozilla.github.io/pdf.js/web/viewer.html I agree that the speed is a lot worse than in Preview.app for example, but it's also not unusable. I will l
4. 4.▲
   by bthorben 12y ago

   Keep in mind that PDF.js is an engine + a viewer. Just a fast engine does not make a nice experience. There are many things in the viewer that one can do to make the experience of using it feel a lot faster.
5. 5.▲
   by bthorben 12y ago

   Filesize has nothing to do with speed most of the time ... Try the PDF Reference document [1], it's pretty fast. The project is very active: in the three month that we investigated it, many of the pdfs that were unusable (e.g. NASAs bu
6. 6.▲
   by bthorben 12y ago

   We realize that the text layer is sometimes a performance problem. We pushed already a lot of improvements to it and there is more too come.