Metrics tab

Timers to control rendering operations (values are in seconds)

• Timeout waiting for Render job to complete - this value indicates how long the render engine will wait for a job request to complete.
• Polling interval for checking queued rendering requests - render requests are queued by having a row added to the TSRENDQUEU table in the Content Manager database. This row will start life having the machine name column unallocated. The render process looks for new work by selecting rows from this table and putting them into an internal work array. This interval determines how often the render processor will look at this table to find new work.
• PDF request generator polling interval - the Render process allows you to set up a number of automated “searches” that will run periodically and add any results to the render work queue. This setting determines how often the processor will run these searches, looking for new records that meet the search criteria.
• Kill render requests if not completed within - when running print requests as part of rendering there are many circumstances that could cause the request to lock up and stop progressing. The render engine has a background thread looking for any rendering print request that hasn’t progressed for this amount of time. It will then kill the request off, leaving the request queued to be processed again later.
• Render jobs progress notification interval - in order to prevent the background render monitor thread from killing off a particular render request, the rendering thread notifies progress at a set interval. This basically notifies the monitor thread that the print function is still running.

Other size limits

• Render request claim size - when the render processor claims new work from the render queue table, it selects a batch of rows from the table and claims them by adding the machine name to the request row. This mechanism allows multiple rendering engines to be configured to process the queue. This setting determines how many queue entries are claimed at one time.
• Suspend PDF request generator if queue is larger than - the PDF request generator will stop if the render queue is larger than this setting. Useful to prevent these searches from overloading the queue.
• Consecutive Failure Limit, Per Document Type - maximum failure limit = 50 - the render processor keeps a counter of the number of failures that have occurred, one for each different document type. To correct this error, once the original error that causes the file type to fail is fixed, restart the event processor, and resubmit or remove any errors in the queue.
• Default - click to set the rendering metrics back to the default settings.