Improving speed is useful but this prescribe a specific technique that might or might not make things faster. Performance is complicated. Also, this is not very actionable: SumatraPDF is fast. How do we decide that it's fast enough (i.e. how do we decide that this request has been completed)?
kjk: the speed of light is fast.
kjk: I would like to be able to hold page-down or scroll the document and see whatever page I arrive on without waiting for it to render, even if I have to wait a bit for the process to fully complete before it's ready for the whole document. as-is, no matter how long I've had a document open, I have to wait whenever I navigate it, which makes navigating within long documents by sight impossible. if i can do this with an image viewer and a folder with a gigabyte of images in it, i don't see why i shouldn't be able to do it with a PDF after some amount of work on the computer's part, even if postscript is more complicated to render than an image.
I like the idea, it is very convenient in most cases. But I think there are some cons to consider: 1- Increase of RAM usage 2- Increase of initial view time 3- Zooming would lead to do the pre-render the whole pdf again 4- Heavy documents (high quality images , hyper detail vectors) would actually have a worse performance because of 2 and 3 And because of that as someone already said, I would like this be optional, better if could be a setting per document
In case preloading would impact performance, I would like this option to be optional (via preferences).
this is what i had in mind. sumatrapdf is low in using cpu and ram but in the future, less than 8 gb is rare so sumatrapdf could prerender the whole document and it's not a problem.
I would be great with at least an option to allow for pre-loading the document. I understand that it is great it works on old and underpowered machines, but on an overpowered machine with plenty of ram it is quite annoying to scroll through blank pages.