HOW TO: Troubleshoot performance problems on PGP Universal Server
Last Updated June 20, 2012
This article describes how to troubleshoot performance problems on PGP Universal Server.
For solving generic performance problems
Verify hardware, kernel type, swap size
1.Ensure that the server hardware is one of the certified hardware platforms as described in the certified hardware list. This list is located in PGP Universal Server Release Notes.
2.PGP Universal Server must be booted from a PAE kernel so that a maximum of 16GB memory can be used.
3.Check if there is sufficient swap size.
The recommended swap size can be calculated using the following formula:
Amount of Physical Memory Swap Space Multiplier
1GB to 2GB 2x
2GB to 8GB 1x
8GB to 16GB 0.67x
Increase the swap size if the current swap size is less than recommended.
For solving problems specific to PGP Universal Server
When server performance is slow
Check log levels
Too much logging reduces PGP Universal Server’s performance.
Set an application’s log level on PGP Universal Server using one of these keywords: debug,info, notice, warning, or error. This keywords list is in decreasing order of the amount of information logged.
Set your log level against your key log level. The setting can be done at an individual application level
or at a global level. The global level setting overrides individual application level settings.
When mail and other communications are slow
In an ATM environment
If you are running PGP products in an asynchronous transfer mode (ATM) environment and experiencing slow mail communication, but your CPU performance is still reasonable, make sure that you have adequate bandwidth allocated to the mail flow. In ATM environments, manually allocate bandwidth amounts for various purposes.
If you see a lot of queuing, ensure that you have adequate bandwidth.
Using DNS configurations
Proper Domain Name System (DNS) configuration ensures that the software performs as intended. PGP Universal Server interfaces require both forward and reverse lookups with the DNS server. Without both records, you might encounter reduced performance.
To ensure that the communication between PGP Universal Server and the clients is as efficient as possible, the network interface cards (NICs) on PGP Universal Server and the switch must match in speed and duplex type. For example, if one side is 100Mbps full duplex, the other side also must be 100Mbps full duplex.
Note: If PGP Universal Server is installed on a VMware system, install VMware Tools to ensure full-duplex communication.
When the NICs do not match, auto-negotiation problems result in:
·Multiple packet collisions followed by retries
If the NICs do not match, replace one or both so that they do match. Symantec recommends using NICs that are full duplex and as fast as possible.
Turn off auto-negotiation using the following command:
ethtool -s eth0 autoneg off
For further reference
Refer to the following article for diagnosing performance issues: