3.4. Performance

Server performance is directly related the volume and type of print jobs being processed. It also depends on the actual function being performed by PriApps.
Where PriApps is not being used to manage and process print queues, for example when simply tracking print usage or managing the deployment of printers and drivers, a single application server can manage thousands of printers.

Where PriApps is being used for more processor intensive functions, such as SSO and Secure Print Release, a load of 200-300 print devices is recommended. The number of users can be a guide to performance but is not a direct factor.

If a large amount of mobile printing is to be done a more powerful server will be required than for an equivalent amount of normal Windows printing. This is because mobile prints need to be rendered on the PriApps Application server whereas Windows prints are typically rendered on client PCs. In the case of printing from Chromebooks, Universal Print by Microsoft, and iOS AirPrint, print jobs are presented as PDF data streams. If the target printer supports PDF directly no rendering on the server will be required, greatly reducing the load on the server, and enabling the same server to process more jobs.

Geographical considerations can also affect server deployment choices. It is unwise to control a printer from a remote location if the network connectivity is not sufficiently reliable and performant, particularly for functions such as SSO and Secure Print Release. PriApps recommends a distributed server deployment in such circumstances.