With modern switched Ethernet networks, bandwidth is rarely a factor when planning PaperCut NG deployments. The bandwidth consumed by PaperCut NG is usually dwarfed by the print document data - e.g. the Postscript spool data sent across the network. Bandwidth does however become a consideration when planning deployments crossing physical site boundaries such as networks linked via a WAN.
PaperCut NG uses an XML based web services protocol for communication between client-to-server and server-to-server. This protocol is very bandwidth efficient and designed to work well on low bandwidth and high latency networks.
Bandwidth consumption can be summarized as follows:
Other than normal print server traffic (standard job spooling), PaperCut NG will generate XML-RPC based Web Services based traffic on port 9191. Connections are made from the print server to the main PaperCut NG server (Primary Server). Normal activity is around 1-2kb of traffic for for each print job. Connections are instigated from the secondary server. Network packets are only sent during printing activity.
Connections are instigated by the client inbound to the server on port 9191 and 9192 (Encrypted SSL). While at idle, the client consumes a few bytes once every minute (a keep-alive heartbeat). During print activity, up to 1-2kb per print job may be consumed depending on client popup settings.
If using account selection popups, the client must download the latest account list from the server whenever it is updated. The accounts are downloaded in a very efficient compressed format (approximately 20 bytes per account). If you have 10's of thousands of accounts, and many clients running on remote sites with limited bandwidth, please see the section called “Managing Large Client Account Lists on Distributed Sites”.
© Copyright 1999-2009. PaperCut Software International Pty Ltd. All rights reserved.