Can Pegasystems recommend specific settings and values for individual operating systems (such as Linux, AIX, or Windows) for best runtime performance and response?
While individual situations may vary, Pegasystems Global Customer Support recommends the following settings for the operating systems listed, for achieving best performance in a production setting. For more information, see the system requirements listed in your Pega Platform™ installation guide.
Monitor CPU usage and address any systems whose CPU usage is greater than 70 percent, as this may indicate potential resource constraints.
CPU utilization should never be more than 70 percent busy due to Process Commander itself.
Linux and Unix
Use these commands to monitor percentage CPU use on Unix/Linux systems:
Commands to monitor percentage CPU use on AIX systems:
Heap size should be below 1.5GB for the IBM JVM with AIX 32-bit Java on Z-series servers; add JVMs and reduce the heap size rather than increasing the heap size on the existing JVM(s). However, for the P-series, 64-bit Java is recommended. 31-bit is not recommended.
The following IBM article discusses heap size and OutOfMemory errors for the IBM JVM and WebSphere application server:
Red Hat Linux
Conform to File System and Storage limits for Maximum x86 per-process virtual address space (or Maximum x86_64 per-process virtual address space, as applicable). Note that the x86 "Hugemem" kernel is not provided in Red Hat Enterprise Linux 5 or 6.
On a 64-bit Solaris system running 32-bit JVMs, the heap size can be close to 4 Gb. To support more users per JVM, you can increase the heap size, however using 64-bit Java is recommended instead.
Use of 64-bit Java, rather than 32-bit Java, is recommended for Windows systems which act as a server hosting Process Commander.
Adjust the DNS lookup setting specific to Ping Interval, to reduce the overhead cost of monitoring in a z/OS environment:
The following IP address caching adjustment may also be necessary: