Performance Problems in 601
CLM 601 WAS Liberty -> JRS 601 (separate machine)
16 GB RAM (8GB for CLM) - 16GB RAM (8GB allocated for JRS)
I can understand during 502/tomcat after a reboot, the first to log in took a long time. With WASLiberty601, the login appears quick on start up, and it takes a while to log in, OK. However, the problem I am having is EVERY DAY this week, when I log in in the morning, it's taking 5-10mins. Sometimes after a long period of idle, it takes time. I logged in, (5-10mins) and it worked fine after that. I went to a couple of meetings and lunch. I came back and I logged in at 2:18pm, it took till 2:29pm to finally log me in to my personal dashboard. Others tried, and they were left waiting as well.
What can I do to problem solve this?
I had the server team and WAS team look at the server. 4GB of the 8GB for Java was in use, Memory of the 16GB machine at 53%. Virtually no CPU usage. 7.xGB available.
Any ideas on what logs or something to look for?
2 answers
Sterling
Is the login time same if you browse to either server? are you using Liberty's own user registry or connected to LDAP? Any different if you use the browser on the server? What is the network connection between the two servers - no unexpected high latency/ping time? You aren't using file shares between them, are you?
Liberty defaults to lazy loading of apps which means there can be a delay the first time you browse to an app (and also when an app is activated by e.g. rich hover). This would account for why the login appears quickly the first time but the app takes longer to appear. However that delay shou;ldn't appear for subsequent logins to the same app while the server is still running, because Liberty will have loaded it.
If you have free memory available on the machines then I would allocate it to jvm - you might be able to allocate 12G in a 16G machine. There are some guidelines (IIRC in the deployment wiki) that the jvm memory allocations for Xmx and Xms should be set to the same, e.g. 12G, and the nursery Xmn should be a third of that, i.e for 12G the Xmn should be 4G.
HTH
Ian
Is the login time same if you browse to either server? are you using Liberty's own user registry or connected to LDAP? Any different if you use the browser on the server? What is the network connection between the two servers - no unexpected high latency/ping time? You aren't using file shares between them, are you?
Liberty defaults to lazy loading of apps which means there can be a delay the first time you browse to an app (and also when an app is activated by e.g. rich hover). This would account for why the login appears quickly the first time but the app takes longer to appear. However that delay shou;ldn't appear for subsequent logins to the same app while the server is still running, because Liberty will have loaded it.
If you have free memory available on the machines then I would allocate it to jvm - you might be able to allocate 12G in a 16G machine. There are some guidelines (IIRC in the deployment wiki) that the jvm memory allocations for Xmx and Xms should be set to the same, e.g. 12G, and the nursery Xmn should be a third of that, i.e for 12G the Xmn should be 4G.
HTH
Ian
Comments
Update:
It just hung for 6 minutes at /jts/admin. When it finally came back, it gave the following message:
The external user registry synchronization is complete. All users have been imported into the Jazz Team Server.
Soooo....is it LDAP (MS Active Directory) that is causing this delay? What are the sync times for LDAP? If I can monitor this, then I might have a clue.
Comments
Comments
Tiago Moura
Mar 18 '16, 3:06 a.m.Donald Nong
Mar 17 '16, 11:09 p.m.1 vote