Caching saves rendering results to a specified location, such as a local disk. When you re-request the rendering results, GroupDocs.Viewer does not render again, but uses the cached results.
As a document can take a long time to render, use caching if you expect to reuse the rendering results.
To enable caching, follow these steps:
Instantiate the desired cache object (for example, FileCache to store document rendering results at the local drive)
Instantiate the ViewerSettings object. Specify the cache object as a parameter of the constructor.
Instantiate the Viewer object. Specify the ViewerSettings object as a parameter of the constructor.
The following code snippet shows how to enable caching and displays the difference between rendering a file and getting the cached results:
constcachePath="cache";constcache=newFileCache(cachePath);constsettings=newViewerSettings(cache);constviewer=newgroupdocs.viewer.Viewer("sample.docx",settings)constoptions=HtmlViewOptions.forEmbeddedResources();constcurrentTimeMillis=Date.now()viewer.view(options);currentTimeMillis=Date.now()-currentTimeMillisconsole.log("Time taken on first call to View method "+currentTimeMillis+" (ms).")currentTimeMillis=Date.now()viewer.view(options)currentTimeMillis=Date.now()-currentTimeMillisconsole.log("Time taken on second call to View method "+currentTimeMillis+" (ms).")
The following image shows a sample console output:
For details, please refer to the following pages:
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.