Retaining pages in memory after long periods out of program

[username132]

If I minimise PDF Xchange Viewer and work in other programs for a while, then return to PDF Xchange Viewer, the page I'm on functions correctly, however when I try to scroll to the next page, the HDD appears to need to spin up for me to continue reading (the pages are blank until they load from the HDD). A more efficient situation would be to maintain the next (and previous) page in memory as well as the current page. In this way, the HDD could spin up in time for subsequent pages and the user would not notice any performance issues unless they scrolled through multiple pages before the HDD could spin up.

[Stefan - PDF-XChange]

Hello username132,

While we do develop and implement memory optimizations in our products, memory management is up to the Operating System, so it might be that your OS has "swapped" some of the memory used by our Viewer to your hard drive, in order to free some more actual RAM for another application that needed it more. Swapping (and then reading from the hard drive) is always slower than using only memory, but there is nothing we can do to prevent that. If you have 4 or more gigabytes of RAM there are some tricks you could do to minimize the swap file without sacrificing performance, but this is a separate topic.

Regards,
Stefan