Server Tuning Guide – CPU Time

Modern business systems are typically more than capable of providing sufficient processing power to the StayLinked Server. Some StayLinked features or business operating systems will require more processing power than others. If the StayLinked Server does not get access to processing in a timely manner, it can cause delayed transactions to the client devices. All StayLinked Servers should be allocated an absolute minimum of two dedicated CPU cores in order to ensure adequate CPU for Java Garbage Collection. Insufficient memory or processor time can result in the unusual growth of the JVM Heap, possibly exceeding the upper memory limit and causing issues or failure of the StayLinked Server process. Most host operating systems offer some diagnostic features allowing visibility of CPU usage for each server process. Monitoring these values during peak usage can give an indication of the CPU requirements of the StayLinked Server process.

One way to detect insufficient processing power is the StayLinked Server Statistic for “Aged Syncs”. These would appear in the StayLinkedStats.log file, which is not enabled by default on older Server installations. Statistics logging can be enabled using the Usage Tracking Features in the StayLinked Administrator. While any server may have an occasional handful of aged syncs, consistent aged syncs or high quantities may be an indication that the StayLinked Server is unable to respond to requests because it is waiting for the available resources from the server operating system. More information on Server Statistics can be found in the documentation for server-side logging features or using the link above.

Note that Virtualization Software Providers offer best practices on various resources and configuration, including maximum CPU utilization.