PaperCut Server Sizing Guide

KB Home   |   PaperCut Server Sizing Guide

Main.PaperCutServerSizingGuide History

Hide minor edits - Show changes to output

October 10, 2018, at 06:37 PM by Aaron Pouliot - Added note about max limit of 3200 queues
Added line 13:
* The number of print queues on a particular print server. PaperCut currently can only monitor up to a maximum of 3200 print queues per each server.  If your server has more print queues than this, you will need to move some of the queues to a PaperCut Secondary Server.
August 01, 2018, at 05:40 PM by Jack Lawless - Deleted paragraph
Deleted lines 12-13:

With so many different factors interacting together, it is not realistic to provide a formula based approach as each site is unique. For these reasons we take a practical approach. We obviously do recommend testing in your environment for your particular organisation size.
August 01, 2018, at 05:40 PM by Jack Lawless - Merging contributions from Art & Aaaron.
Changed lines 3-8 from:
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 will help you come up with an answer
that makes sense for
you.

!!!''"Why doesn't PaperCut just provide a simple formula based answer?"''

to:
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.
Deleted line 6:
* Your environment's network speeds and topology.
Changed line 11 from:
* Use of our [[https://www.papercut.com/tour/track-copiers/|PaperCut embedded solution on Multi-Function Devices]] if you're using PaperCut MF. Different copier platforms have different performance profiles depending on whether the performance load is on the MFD itself or is a newer Web Services platform (performance load on the Server instead).
to:
* Use of our [[https://www.papercut.com/tour/track-copiers/|PaperCut embedded solution on Multi-Function Devices]] if you're using PaperCut MF.
Changed lines 16-17 from:
When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore.
to:
!!!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 [[https://www.papercut.com/kb/Main/CommonScalabilityQuestions | here]]
.
Changed lines 24-27 from:
Don't skimp on CPU resources! We generally always recommend a starting baseline of 2x CPUs and then to extrapolate from there depending on your environment size and all the consideration outlined on this KB. See the Server Sizing Table at the bottom of the page for additional help.

''Note: If a Virtualised Server is being used, don't forget to set a static and appropriate reservation of your CPU resources to the Print Server.''

to:
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.
Changed lines 28-41 from:
PaperCut uses {+1/4 of the available memory of the server by default+}. So if you are building a VM specifically for dedicated use of PaperCut NG or MF, start off with a 4GB VM, and allow PaperCut to use up to 1/2 of the memory by making  [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage | this RAM configuration change]] .

''Note: If a Virtualised Server
is being used, don't forget to set a static and appropriate reservation of your RAM resources to the Print Server.''

''Note...2?!: Due to the way PaperCut operates as a Java encoded program, having more RAM than is required for your environment can actually negatively impact your printing performance due to the way the systematic Garbage Collection process run through your total RAM: sometimes, less is more!''

!!!Database Storage.

This is the base data size plus number of print jobs per month (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 [[https://www.papercut.com/products/ng/manual/apdx-capacity-planning.html#cap-plan-db-sql-server | here]].

!!!Print Server Storage.

Any print servers will require good disk I/O and disk space for print spooling (10+Gb depending on the number and size of the print
jobs). The print server is responsible for print job analysis which is an intensive IO operation, modern enterprise class server disk IO support will be fine.
to:
When building a [[https://www.papercut.com/kb/Main/PaperCutOnVM|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 [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage|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!

!!Storage

!!!Database

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 [[https://www
.papercut.com/products/ng/manual/apdx-capacity-planning.html#cap-plan-db-sql-server | here]].

!!!Print Server

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 [[https://www.papercut.com/products/mf/system-requirements|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.
Changed lines 46-47 from:
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 [[https://www.papercut.com/tour/private-cloud|remotely]].
to:
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 [[https://www.papercut.com/tour/private-cloud|Private Cloud]].
Deleted lines 212-213:

We also have additional information regarding your environment growing and scaling over time [[https://www.papercut.com/kb/Main/CommonScalabilityQuestions | here]].
July 31, 2018, at 10:51 AM by Jack Lawless - Merging and consolidating information from previous "What Size Servers Do I Need" KB.
Changed lines 3-14 from:
The table below shows guidelines for the server specifications that are required to support PaperCut in order to give consistent performance given most patterns of use. 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 [[https://www.papercut.com/tour/private-cloud|remotely]].

When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore.

Always evaluate your host solution before deploying in order to make an informed decision regarding CPU load and memory usage.

For more information on increasing the memory allocated to the PaperCut Application Server, take a look at the [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage|Increasing Max Memory Usage]] article.

[[http://www.papercut-mf.com/buy/|PaperCut Authorized Solution Centers]] are able to offer architecture and infrastructure advice for large deployments. Also please see our [[https://www.papercut.com/products/ng/system-requirements/|System Requirements Article]] for more guidelines on server system requirements.

'''Please Note: The specifications in the table below are meant as a guide only!'''

to:
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 will help you come up with an answer
that makes sense for you.

!!!''"Why doesn't PaperCut just provide a simple formula based answer?"''

There are a large number of factors that affect the size of systems needed. For example:

* Your environment's network speeds and topology.
* Number of average and peak users simultaneously using the system.
* Type of print jobs (file size, printer language in use, printer options selected, print scripts in use etc.).
* Use and configuration of [[https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/find-me-printing.html|Find-Me]] printing queues.
* Features such as [[https://www.papercut.com/products/mobility-print/|Mobility Print]], [[https://www.papercut.com/tour/web-print/|Web Print]], [[https://www.papercut.com/tour/email-to-print/|Email to Print]],  [[https://www.papercut.com/tour/print-archiving/|Print Archiving]] etc.
* Use of our [[https://www.papercut.com/tour/track-copiers/|PaperCut embedded solution on Multi-Function Devices]] if you're using PaperCut MF. Different copier platforms have different performance profiles depending on whether the performance load is on the MFD itself or is a newer Web Services platform (performance load on the Server instead).
* Use of [[https://www.papercut.com/tour/payment-gateways/|Payment Gateways]] and other third party external interfaces can also impact performance and are not under the control of the PaperCut application.

With so many different factors interacting together, it is not realistic to provide a formula based approach as each site is unique. For these reasons we take a practical approach. We obviously do recommend testing in your environment for your particular organisation size.

When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore.

!!!Server CPU

Don't skimp on CPU resources! We generally always recommend a starting baseline of 2x CPUs and then to extrapolate from there depending on your environment size and all the consideration outlined on this KB. See the Server Sizing Table at the bottom of the page for additional help.

''Note: If a Virtualised Server is being used, don't forget to set a static and appropriate reservation of your CPU resources to the Print Server.''

!!!Server RAM

PaperCut uses {+1/4 of the available memory of the server by default+}. So if you are building a VM specifically for dedicated use of PaperCut NG or MF, start off with a 4GB VM, and allow PaperCut to use up to 1/2 of the memory by making  [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage | this RAM configuration change]] .

''Note: If a Virtualised Server is being used, don't forget to set a static and appropriate reservation of your RAM resources to the Print Server.''

''Note...2?!: Due to the way PaperCut operates as a Java encoded program, having more RAM than is required for your environment can actually negatively impact your printing performance due to the way the systematic Garbage Collection process run through your total RAM: sometimes, less is more!''

!!!Database Storage.

This is the base data size plus number of print jobs per month (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 [[https://www.papercut.com/products/ng/manual/apdx-capacity-planning.html#cap-plan-db-sql-server | here]].

!!!Print Server Storage.

Any print servers will require good disk I/O and disk space for print spooling (10+Gb depending on the number and size of the print jobs). The print server is responsible for print job analysis which is an intensive IO operation, modern enterprise class server disk IO support will be fine.

!!Server Sizing Table

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 [[https://www.papercut.com/tour/private-cloud|remotely]].

PaperCut [[http://www.papercut-mf.com/buy/|Authorized Solution Centers]] are able to offer architecture and infrastructure advice for large deployments if you're a current PaperCut MF customer. Also please see our [[https://www.papercut.com/products/ng/system-requirements/|System Requirements]] page for more guidelines on minimum and recommended server requirements.

'''Note: The specifications in the table below are meant as a guide only! Nothing substitutes volume testing before going live!'''

Changed lines 213-214 from:
'''+RDBMS:''' Separate database servers are recommended where noted. See [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|the PaperCut Manual]] for more information.
to:
'''+RDBMS:''' Separate database servers are recommended where noted. See the[[https://www.papercut.com/products/ng/manual/ch-ext-db.html|PaperCut Manual]] for more information.

We also have additional information regarding your environment growing and scaling over time [[https://www.papercut.com/kb/Main/CommonScalabilityQuestions | here]]
.
Changed line 218 from:
''Categories:'' [[Category.Cloud|+]], [[Category.Administration|+]], [[Category.Architecture|+]]
to:
''Categories:'' [[Category.Administration|+]], [[Category.Architecture|+]], [[Category.Cloud|+]], [[Category.Implementation|+]]
Changed line 220 from:
[-Keywords: private, cloud, remote, vps, virtual, machine, vm, server, sizing, guide, size, size guide, database, resource, space-]
to:
[-Keywords: private, cloud, remote, vps, virtual, machine, vm, server, sizing, guide, size, size guide, database, resource,  requirements, system requirements, resources -]
May 11, 2018, at 11:25 PM by timg - Added link to Increase memory article.
Deleted lines 6-7:
'''Please Note: The specifications in the table below are meant as a guide only!'''
Changed lines 9-11 from:
[[http://www.papercut-mf.com/buy/|PaperCut Authorized Solution Centers]] are able to offer architecture and infrastructure advice for large deployments.

Please see our
[[https://www.papercut.com/products/ng/system-requirements/|System Requirements Article]] for more guidelines on server system requirements.
to:
For more information on increasing the memory allocated to the PaperCut Application Server, take a look at the [[https://www.papercut.com/kb/Main/IncreaseMaxMemoryUsage|Increasing Max Memory Usage]] article.

[[http://www
.papercut-mf.com/buy/|PaperCut Authorized Solution Centers]] are able to offer architecture and infrastructure advice for large deployments. Also please see our [[https://www.papercut.com/products/ng/system-requirements/|System Requirements Article]] for more guidelines on server system requirements.

'''Please Note: The specifications in the table below are meant as a guide only!'''
March 28, 2018, at 10:24 PM by 139.130.165.134 -
Changed line 175 from:
'''+RDBMS:''' Seperate database servers are recommended where noted. See [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|the PaperCut Manual]] for more information.
to:
'''+RDBMS:''' Separate database servers are recommended where noted. See [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|the PaperCut Manual]] for more information.
March 03, 2017, at 08:11 PM by Adam Byer - received a ticket regarding system requirements via server sizing guide article, added link
Added lines 12-13:

Please see our [[https://www.papercut.com/products/ng/system-requirements/|System Requirements Article]] for more guidelines on server system requirements.
Changed lines 3-5 from:
The table below shows guidelines for the server specifications that are required to support PaperCut in order to give consistent performance given most patterns of use. These guidelines apply both to physical hardware and to virtual servers / virtual machines hosted locally or [[https://www.papercut.com/tour/private-cloud|remotely]].

When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore.
to:
The table below shows guidelines for the server specifications that are required to support PaperCut in order to give consistent performance given most patterns of use. 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 [[https://www.papercut.com/tour/private-cloud|remotely]].

When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore. 
November 06, 2015, at 06:04 AM by Debbie - PC-6914
Changed line 44 from:
1GB RAM
to:
2GB RAM
Changed line 47 from:
2GB RAM
to:
4GB RAM
Changed line 55 from:
2GB RAM
to:
4GB RAM
December 08, 2014, at 04:15 AM by josh - Added keywords, this was hard to find.
Changed line 178 from:
[-Keywords: private, cloud, remote, vps, virtual, machine, vm, server, sizing, guide -]
to:
[-Keywords: private, cloud, remote, vps, virtual, machine, vm, server, sizing, guide, size, size guide, database, resource, space-]
Changed lines 5-6 from:
When deploying PaperCut it recommended that virtual servers are used where possible for easy scaling and quick backup / restore.
to:
When deploying PaperCut it is recommended that virtual servers are used where possible for easy scaling and quick backup / restore.
October 14, 2014, at 11:34 PM by 203.222.91.204 -
Changed line 31 from:
'''1000\\
to:
'''1,000\\
October 09, 2014, at 05:33 AM by 203.222.91.204 -
Changed line 176 from:
''Categories:'' [[Category.Servers|+]], [[Category.Cloud|+]], [[Category.Administration|+]], [[Category.Architecture|+]]
to:
''Categories:'' [[Category.Cloud|+]], [[Category.Administration|+]], [[Category.Architecture|+]]
October 09, 2014, at 05:32 AM by 203.222.91.204 -
October 09, 2014, at 05:32 AM by 203.222.91.204 -
Added lines 1-178:
(:title PaperCut Server Sizing Guide:)

The table below shows guidelines for the server specifications that are required to support PaperCut in order to give consistent performance given most patterns of use. These guidelines apply both to physical hardware and to virtual servers / virtual machines hosted locally or [[https://www.papercut.com/tour/private-cloud|remotely]].

When deploying PaperCut it recommended that virtual servers are used where possible for easy scaling and quick backup / restore.

'''Please Note: The specifications in the table below are meant as a guide only!'''

Always evaluate your host solution before deploying in order to make an informed decision regarding CPU load and memory usage.

[[http://www.papercut-mf.com/buy/|PaperCut Authorized Solution Centers]] are able to offer architecture and infrastructure advice for large deployments.

----

(:comment ***** Private Cloud Printers vs Users VM Sizing Guide **************************************************** :)

(:table border=1 width=100% cellspacing=5 class=issues :)
(:cellnr class=cnr :)
'''Printers\\
vs Users'''
(:cell class=top :)
'''5\\
Printers'''
(:cell class=top :)
'''20\\
Printers'''
(:cell class=top :)
'''100\\
Printers'''
(:cell class=top :)
'''1000\\
Printers'''
(:cell class=top :)
'''5,000\\
Printers'''
(:cell class=top :)
'''10,000\\
Printers'''
(:comment ******************************  1000 Users  **************************************************** :)
(:cellnr class=side :)
'''1,000 Users'''
(:cell :)
1 CPU\\
1GB RAM
(:cell :)
2 CPUs\\
2GB RAM
(:cell colspan=4 class=blank :)
 
(:comment ******************************  5000 Users  **************************************************** :)
(:cellnr class=side :)
'''5,000 Users'''
(:cell :)
2 CPUs\\
2GB RAM
(:cell :)
2 CPUs\\
4GB RAM
(:cell :)
2 CPUs\\
4GB RAM
(:cell colspan=3 class=blank :)
 
(:comment ******************************  10,000 Users  **************************************************** :)
(:cellnr class=side :)
'''10,000 Users'''
(:cell :)
3 CPUs\\
4GB RAM
(:cell :)
3 CPUs\\
4GB RAM\\
'''+ RDBMS'''
(:cell :)
3 CPUs\\
4GB RAM\\
'''+ RDBMS'''
(:cell :)
3 CPUs\\
8GB RAM\\
'''+ RDBMS'''
(:cell colspan=2 class=blank :)
 
(:comment ******************************  20,000 Users **************************************************** :)
(:cellnr class=side :)
'''20,000 Users'''
(:cell :)
4 CPUs\\
6GB RAM
(:cell :)
4 CPUs\\
6GB RAM\\
'''+ RDBMS'''
(:cell :)
4 CPUs\\
6GB RAM\\
'''+ RDBMS'''
(:cell :)
4 CPUs\\
8GB RAM\\
'''+ RDBMS'''
(:cell :)
4 CPUs\\
8GB RAM\\
'''+ RDBMS'''
(:cell class=blank :)
 
(:comment ******************************  60,000 Users **************************************************** :)
(:cellnr class=side :)
'''60,000 Users'''
(:cell class=blank :)
 
(:cell :)
4 CPUs\\
6GB RAM\\
'''+ RDBMS'''
(:cell :)
4 CPUs\\
6GB RAM\\
'''+ RDBMS'''
(:cell :)
8 CPUs\\
12GB RAM\\
'''+ RDBMS'''
(:cell :)
8 CPUs\\
16GB RAM\\
'''+ RDBMS'''
(:cell :)
10 CPUs\\
16GB RAM\\
'''+ RDBMS'''
(:comment ******************************  100,000 Users **************************************************** :)
(:cellnr class=side :)
'''100,000 Users'''
(:cell colspan=2 class=blank :)
 
(:cell :)
4 CPUs\\
8GB RAM\\
'''+ RDBMS'''
(:cell :)
8 CPUs\\
16GB RAM\\
'''+ RDBMS'''
(:cell :)
10 CPUs\\
16GB RAM\\
'''+ RDBMS'''
(:cell :)
10 CPUs\\
16GB RAM\\
'''+ RDBMS'''
(:comment ******************************  400,000 Users **************************************************** :)
(:cellnr class=side :)
'''400,000 Users'''
(:cell colspan=3 class=blank :)
 
(:cell :)
10 CPUs\\
32GB RAM\\
'''+ RDBMS'''
(:cell :)
10 CPUs\\
32GB RAM\\
'''+ RDBMS'''
(:cell :)
10 CPUs\\
32GB RAM\\
'''+ RDBMS'''
(:tableend:)

'''+RDBMS:''' Seperate database servers are recommended where noted. See [[https://www.papercut.com/products/ng/manual/ch-ext-db.html|the PaperCut Manual]] for more information.

----
''Categories:'' [[Category.Servers|+]], [[Category.Cloud|+]], [[Category.Administration|+]], [[Category.Architecture|+]]
----
[-Keywords: private, cloud, remote, vps, virtual, machine, vm, server, sizing, guide -]

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 October 10, 2018, at 06:37 PM
Printable View   |   Article History   |   Edit Article