ITPAM Production instance is running very slow and showing delayed response.

Products

• CA Process Automation Base

Issue/Introduction

In our production environment, ITPAM instance is running very slow and showing very delayed response when we click on any operator or feature. It also takes lot of time while doing certain operations. Specifically, the problem being experienced is: navigating the ITPAM web UI from their workstations. When navigating the ITPAM web UI from a system on the same network as the ITPAM server, the problem does not exist. 

Environment

Release : 4.3

Component : IT Process Automation

Cause

Network latency/issue. 

Resolution

If you are navigating ITPAM from the ITPAM server, or on a server that's on the same local network as the ITPAM server, and experiencing slowness problems then please open an issue with ITPAM technical support.

If you are only experiencing slowness problems on remote servers then please see the "Additional Information" section for ideas on tests to run. Chances are likely that results from those tests will indicate a network latency problem that needs to be discussed/fixed by the network team. 

 

Additional Information

The following tests may help you confirm that this is a network problem.

From a server on the same network as the ITPAM server:

• Open a browser and access the UI.
• Trying pinging the ITPAM server(s) hostname and/or network/loadBalancer alias. 
• Depending on your ITPAM environment, ITPAM may need to transfer several 10's of kb worth of data while navigating. You can try and simulate how the network will handle this much data by running:
  • ping -l 23000 <itpam servername>
    Note: As of the time of this writing, the maximum packet size ping will allow is 65000. 
• Open a browser and access the UI. Enable developer tools to see how much data is being transferred and how long it is taking to receive the data. 

Execute the same tests, outlined above, on the machine(s) where you have this navigation slowness problem. Compare the results from this machine to the results from the server on the same local network as the ITPAM server.

Another test you can run is to capture network packets (Wireshark) on both the node where you are browsing ITPAM from and also on the ITPAM server. If the tests above show a clear descrepancy then it is likely that analyzing the network captures will show that the delay is while transferring the network packets between the two systems - not with ITPAM receiving the request and then taking a long time to respond.