Harlequin RIP SDK

Metadata collected while processing the job. More...

#include "rf_reply_msgs.h"

Data Fields

size_t size
 
int elapsed_job_time_ms
 
int active_job_time_ms
 
int total_job_time_ms
 
int total_job_interpretation_time_ms
 
int average_page_interpretation_time_ms
 
int maximum_page_interpretation_time_ms
 
int total_job_rendering_time_ms
 
int average_page_rendering_time_ms
 
int maximum_page_rendering_time_ms
 
int average_page_memory_kb
 
int maximum_page_memory_kb
 

Detailed Description

Metadata collected while processing the job.

Field Documentation

◆ active_job_time_ms

int RF_JOB_COMPLETED_METADATA::active_job_time_ms

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 milliseconds. In the first scenario above (there is already a job of the same or higher priority running), the time waiting for 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.

◆ average_page_interpretation_time_ms

int RF_JOB_COMPLETED_METADATA::average_page_interpretation_time_ms

Average interpretation time per page in milliseconds.

◆ average_page_memory_kb

int RF_JOB_COMPLETED_METADATA::average_page_memory_kb

Average peak memory used while processing pages in the job (kilobytes).

◆ average_page_rendering_time_ms

int RF_JOB_COMPLETED_METADATA::average_page_rendering_time_ms

Average rendering time per page in milliseconds.

◆ elapsed_job_time_ms

int RF_JOB_COMPLETED_METADATA::elapsed_job_time_ms

Elapsed Time is the time from accepting a job until all pages from the job are completed in milliseconds. 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.

◆ maximum_page_interpretation_time_ms

int RF_JOB_COMPLETED_METADATA::maximum_page_interpretation_time_ms

Maximum interpretation time for a page in milliseconds.

◆ maximum_page_memory_kb

int RF_JOB_COMPLETED_METADATA::maximum_page_memory_kb

Maximum peak memory for a page (kilobytes).

◆ maximum_page_rendering_time_ms

int RF_JOB_COMPLETED_METADATA::maximum_page_rendering_time_ms

Maximum rendering time for a page in milliseconds.

◆ size

size_t RF_JOB_COMPLETED_METADATA::size

Size of this structure for versioning. If the size is zero it means no metadata was passed back at all.

◆ total_job_interpretation_time_ms

int RF_JOB_COMPLETED_METADATA::total_job_interpretation_time_ms

Total time spent interpreting pages in milliseconds.

◆ total_job_rendering_time_ms

int RF_JOB_COMPLETED_METADATA::total_job_rendering_time_ms

Total time spent rendering pages in milliseconds.

◆ total_job_time_ms

int RF_JOB_COMPLETED_METADATA::total_job_time_ms

Total time spent interpreting and rendering pages in milliseconds.


The documentation for this struct was generated from the following file: