How much memory is needed?
No exact number can be given as the recommendation for the amount of memory needed for a system running InfoPrint Manager. The amount of memory depends on how many jobs are going through the system at what frequency, the size, complexity, and data type of the jobs, and what else is running on the system. Also, the number of queues and actual destinations impact memory utilization.
With InfoPrint Manager, the more memory the better. InfoPrint Manager performs best when it has enough memory that it does not need to use paging space. That is, the more paging space it must use, the worse the performance.
What defines a memory bound system? If the number of active virtual memory pages exceed the amount of real memory pages, page space is used for those pages that cannot be kept in real memory.
To determine if InfoPrint Manager for Linux is using paging space, use the vmstat, free or swapon -s command. With vmstat, look at the swpd memory, swap si (swap in), and swap so (swap out) columns. On a system with no paging, these columns should remain on zero as much as possible. On a machine with memory constraints, you will see the free memory column going toward zero, and then swapping begins.
To start the vmstat command, enter:
vmstat delay count
For information and recommendations for changing values for your configuration, see chapter 2.3.3 - Virtual Memory Statistics (vmstat) from RedHat Enterprise Linux 7 Performance Tuning Guide available at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Performance_Tuning_Guide/index.html.