#Papercut ng webprint pdf#
#Papercut ng webprint drivers#

Historical data is another good tool for tuning your Web Print scaling setup. TIP You might need to manually refresh the page to keep across the changes in job status.Īveraging out the wait times incurred for test jobs during these periods of sustained high load provides an idea of the average time it takes to process a Web Print job in your current environment. On the Web Print page, time how long it takes for each job to progress in the queue from having a Status of Queued in position to Finished: Queued for printing.

#Papercut ng webprint pdf#

Good test documents would be a one page PDF and a one page Microsoft Word document. You can test if this is the case by submitting a number of test Web Print jobs during a peak print period, and timing how long it takes for the job to process. If, however, the number of pending jobs peaks at random points in time, the average wait time might not be an issue. A large number of pending Web Print jobs that rarely or never varies during printing hours, might indicate that users are experiencing consistently high wait times. You can use a monitoring tool to accurately track how this value changes over time. In the System Health Monitoring section, click the Detailed system information link. For more information about this endpoint, see Base system health URL.Ī direct link to this endpoint is available in the Admin web interface: You can use this data to determine the average number of pending jobs as well as the maximum number during peak periods. The Print System Health interface provides a monitoring endpoint that tracks the number of pending print jobs in a Web Print queue at a specific point in time.

To statistically determine the number of Web Print servers you need to adequately handle your throughput, you should evaluate the number of pending jobs your system has awaiting Web Print processing. Determine the number of pending Web Print jobs NOTE The use of multiple Web Print servers is available in PaperCut NG/MF 16.2 and later. You will need to balance the acceptable average wait time that is appropriate for your users, against the resources needed to deploy additional Web Print servers.

#Papercut ng webprint drivers#

While we recommend a minimum of two Web Print servers as a starting point, the unique demands and performance characteristics of your environment are the key drivers in determining what you need. While you can simply continue to add Web Print Servers until the Web Print performance during peak printing hours is acceptable, sites with particularly demanding throughput will benefit from using statistics for their capacity planning.Īnalyzing these statistics will help you plan your Web Print deployment. However, two Web Print Servers might not be enough for sites that see very high Web Print throughput. Best practices in server management recommend building redundancy into your network and monitoring the health of your environment. Using only one Web Print server causes a single point of failure and potential bottlenecks.

When using Sandbox mode, we recommend a minimum of two Web Print servers. PRODUCTS FEATURED Scaling your Web Print environment