Load Testing a PaperCut Setup
Last modified on 15 August 2020 01:55 PM
Testing PaperCut NG/MF in a realistic way can be quite difficult. There are a number of layers in the application that get exercised when a print job is processed. Any practical load testing needs to exercis all layers. Here are a few tips and tools:
Printing Load Testing
A good way of load testing printing is to use a simple “batch printing” script across multiple systems. Here is an example batch file for Windows:
FOR /L %%A IN (1,1,100) DO (copy /B testdoc.ps "\\print-server\Test Printer" && ping -n 2 localhost)
This will print 100 jobs of a representative PostScript test document to the server with a small delay between jobs. It’s suggested that you run this script in parallel on at least 10 workstations.
The test file can be simply generated using the Windows “Print to File” feature.
Client Load Testing
You can test client load and activity with a special command-line option on the standard PaperCut client software. Running
pc-client.exe --stress-test ServerIP NumClients
\\print-server\PCClient\win\pc-client.exe --stress-test 10.1.1.44 100
To simulate a real network environment we’d recommend running this command on at least 10 separate workstations in different parts of the network (different latency profiles). Hence this will simulate 1,000 clients.
During load testing we’d recommend checking:
CPU and Memory logging is of limited value and is more useful for comparison reasons rather than “gaining knowledge”. As you’d expect under a stress test like this, usually CPU will hit 100% while jobs are being processed.