PaperCut Server Sizing Guide
Last modified on 09 August 2020 07:08 PM
Before installing PaperCut, Sys Admins often want to know what type of hardware they need to run a quick and responsive system in their specific environments. That’s quite a hard question to answer, but hopefully, these guidelines provide an answer that makes sense for you.
There are a large number of factors that affect the size of systems needed. For example:
Scalability & Disaster Recovery
We recommend virtual instead of dedicated physical servers. Virtual machines benefit from using any reserved amount of the host’s complement of processing, storage, and memory resources as well as the vendor’s built-in or customised back-up and restore capabilities. The basic recommendation for CPU, RAM, and Storage is for them to be to set statically rather than dynamically.
We also have additional information regarding your environment growing and scaling over time here.
Don’t skimp on CPU resources! The typically recommended CPU requirement is to start with two and then to extrapolate from there depending on the size of your organisation and this KB’s suggestions. See the Server Sizing Table at the bottom of the page for additional help.
When building a Virtual Server, specifically for PaperCut NG or MF, start at 4GB of RAM and make sure the memory is reserved, not dynamically allocated.
The PaperCut application will use 1/4 of the server’s available memory by default, but it’s possible to configure PaperCut to use up to 1/2 of the memory by making the change discussed here.
The PaperCut application itself is a “process virtual machine” operating in a Java runtime environment. The JRE’s garbage collection process tries to keep the memory as neat as possible which means having more RAM than required for your organisation can negatively impact the application’s performance. Sometimes, less is more!
Consider that the PaperCut database grows at an approximate rate of 4.5Mb per 10,000 jobs. For example: allowing for 4 print jobs per user and a 30% increase that comes out at just under 1/2 Gb over three years. As our storage requirement is so low we do not suggest archiving. You can calculate your own value using the guidelines here.
Print servers require disks capable of fast data transfer and enough space for print job spooling. The minimum requirement overall is 100 GB of free space as discussed here. (10+ GB depending on the number and size of the print jobs). PaperCut’s job analysis is an intensive Read/Write operation, and modern enterprise-class server disks should support its basic requirements.
The table below shows guidelines for the server specifications that are required to support PaperCut NG or MF in order to give consistent performance for a-typical printing use at a site. Please note that Users refers to the number of active users per day. These guidelines apply both to physical hardware and to virtual servers / virtual machines hosted locally or in a Private Cloud.
Note: The specifications in the table below are meant as a guide only! Nothing substitutes volume testing before going live!
+RDBMS: Separate database servers are recommended where noted. See the PaperCut Manual for more information.