How fast should EngageOne Vault render a document between 200 and 500 pages

UPDATED: July 5, 2018

Each rendering engine is capable of rendering at a certain rate.  The rate is affected by several factors, among these are the following:

1. The speed of the computer and the amount of physical memory available
2. The input format - certain input formats are more complex to render than other input formats.  
3. The output format - certain output formats are more complex to render than other output formats

In general, the rendering speed is normally in the range of 10 pages per second, but the original load time can vary depending on the type of document requested.

If this is a Postscript document, the headers have to be downloaded from the server, therefore larger headers means more transfer time.
The headers need to be decompressed from the drp file. Larger blocks (needed for larger headers) results in more time to decompress.
Before 7.0, the large compressed block sizes had to be explicitly set and applied to pages not just headers. That slowed page retrieval as well.
Once the rendering engine has the header, it is transmitted to the e2ps subprocess and executed by the Ghostscript library. Larger headers tend to take longer to execute. But there are some constructs that Ghostscript handles faster than other so it can also depend on the commands used by the header.
The Ghostscript lock tends to delay Postscript rendering requests unless GhostscriptParallel=1 is used (default in later versions).


Environment Details

Product Feature: Render



  • No Downloads