Monitoring Scalable RIP

This page applies to Harlequin v13.1r0 and later; and to Harlequin Core but not Harlequin MultiRIP

As shown in the example in Scalable RIP Quick start the Scalable RIP reports different details in the log output to those from a single RIP.

Jobs are submitted and processed asynchronously, so the Total time reported by the RIP is just the time required to submit the job to the Scalable RIP's job controller. The Scalable RIP reports:

When it accepts a job for processing
When it starts processing pages from the job, and
When it has completed (or failed to complete) all pages from the job.

On completion, it reports three times:

Elapsed Time is the time from accepting a job until all pages from the job are completed. If there is a job of the same or higher priority running already, then the job will not start until that job is finished, so the elapsed time will include the amount of time spent waiting to start. Similarly, if a higher priority job interrupts the job, the elapsed time will include the time spent waiting for the higher priority job.

Active Time is the time from starting to process the first page range of a job until all pages from the job are completed. In the first scenario above (i.e., if there is already a job of the same or higher priority running), the time waiting to start will not be included in the active time. However, in the second case where a job is interrupted after the first page range has been started, the active time will include time spent waiting for the higher priority job.

Schedule Time is the accumulated time for processing all page ranges in the job, measured from the time the page range is sent to a Farm RIP for processing until the time the page range completion was received from the Farm RIP. It is not an exact measure of the amount of processing time used because the page range processing is pipelined to prevent idle RIPs. The request to process a page range can be sent before a Farm RIP is actually available, so the Schedule Time will include time waiting for the previous page range to complete for each page range.