Skip to main content

Describes the amount of resources that are consumed when running a Rumba printer session as a Windows service.

Problem:

How many Rumba printer sessions can be configured as Windows services? Is there a hard coded limit that should not be exceeded?

Resolution:

There is no hard-coded limit on the number of printer servers you can run. However, each printer service uses a specific amount of machine resources, and this may prove a practical limit. Some customers are not able to run more than 32 services on a machine because of limited resources.

Each printer service uses approximately 8 MB of memory when it is sitting idle. It will allocate more resources when processing a print job.

If you are having problems starting a new Rumba printer session as a service, check that the server is not running out of resources. Stopping sessions that are already running sessions may sometimes release enough resources to start others. If you look in the Task Manager on your server, the printer services should show up as PrnSrvr.bin. You might want to check how much memory is being consumed and how much is available on your server.

Incident Number: 2422558

Old KB# 14895

#Rumba
#SupportTips/KnowledgeDocs