Load Testing a PaperCut Setup

KB Home   |   Load Testing a PaperCut Setup

Main.LoadTesting History

Hide minor edits - Show changes to output

April 22, 2013, at 03:46 AM by 203.12.22.88 -
Changed lines 6-7 from:
A good way of load testing printing is to use a simple "batch printing" script across multiple systems.  Here is an example batch file:
to:
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:
Changed lines 12-13 from:
It prints 50 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.
to:
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.
Changed lines 40-42 from:
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 CUP will hit 100% while jobs are being processed.

to:
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.

Changed line 46 from:
[-Keywords: stress testing, performance profile, performance testing, p -]
to:
[-Keywords: stress testing, performance profile, performance testing, monitoring -]
Changed lines 1-4 from:
(:title Load Testing a PaperCut setup:)

'''NOTE:'''  This article is a work in progress.  At the moment it's just notes:

to:
(:title Load Testing a PaperCut Setup:)
Changed lines 40-42 from:
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 you'll hit 100% while jobs are being analized.

to:
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 CUP will hit 100% while jobs are being processed.

Added lines 1-48:
(:title Load Testing a PaperCut setup:)

'''NOTE:'''  This article is a work in progress.  At the moment it's just notes:

Testing PaperCut 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 excise 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 /L %%A IN (1,1,100) DO (copy /B testdoc.ps "\\print-server\Test Printer" && ping -n 2 localhost)
@]

It prints 50 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@] on the client with the following option will simulate the client load of 100 workstations:

[@
    pc-client.exe --stress-test ServerIP NumClients
@]

e.g.

[@
    \\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. 

!!!Performance Monitoring
During load testing we'd recommend checking:

* That all jobs sent are accounted for and logged as expected
* The clients don't raise any disconnection errors during the activity
* Check the PaperCut Application Log for any error events
* Check the database system for any error or warning events
* Check the server OS system logs for any error events

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 you'll hit 100% while jobs are being analized.


----
''Categories:'' [[Category.Implementation|+]]
----
[-Keywords: stress testing, performance profile, performance testing, p -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on April 22, 2013, at 03:46 AM
Printable View   |   Article History   |   Edit Article