Question
Infosys LTD
AU
Last activity: 23 Feb 2017 2:22 EST
Production Slowness for Users
Hi Team,
We are using Pega 6.2 SP2 and Jboss 5.1 as web server.
We are facing slowness issues across the platform and unfortunately are unable to find the Root cause whether its App server, DB server or the Storage/Networks.
We have raised this with the Oracle team and also with the Red hat support team.
Would also like to check with Pega technicians about the issue.
Issue :
- Users are facing latency in getting into the app through single sing on, we have checked with the Single sign on team and have got a response that the users are waiting for your app server to respond and the slowness lies with your app.
Would need your help to understand is there any Pega config for number of users who can logon to a server and once the threshold is reached other requesters need to wait for connection to be made available.
- AJAX issues on screen for the almost all the users.
Please advise.
Thanks
Dalbir Singh
Accepted Solution
Infosys LTD
AU
Hi Guys,
Thanks for your valuable responses actually the issue which we were facing was more over the network side. The link between the Darabase and tye storage was a 1 GBPS link and as we have shared database amoung applications we were pumping more than that hence clogging the storage link. Due to this the data retrieval use to take lot of time. We have now migrated the storage link from 1 GB to 10 GB on the network layer and things are moving faster than ever before.
But, still at some points we do see a sudden hike on the link from average load of 1.5 GB to 4 GB. We are still hunting for that heavy operation which should be causing this. We have taken few reports like AWR, ASH reports from DB. If anyone can lend additional hand on this it would be great.
Thanks a lot everyone.!!!
Pegasystems Inc.
IN
Hi Dalbir,
Please share the pegarules and alert log. Also, try manually executing some PRPC related select query directly from DB and see how much time it takes to provide the result.
Telstra
AU
Hi,
Actually we are interested to understand where we can see maximum number of requestor allow to login in our system.
Where we can find these configurations ?
Thanks
PEG
PL
We could not say how many requestors can login at a time. But depending on the available memory, you could take a wild guess.
Eg: Lets see, you have a browser requestor and it took around 30 mb of page size, you could guess how many requestors can log in for available memory.
Pegasystems Inc.
IN
Hi dalbir , as per my understanding RDs also some times cause slowness in accessingthe application can you check whether any of the RD exexcution is takign long time .Or any bulk process loading is happenig on the server
Updated: 24 Jan 2017 8:25 EST
Capgemini Sverige AB
SE
Hi Dalbir,
Check if there is any batch job has been running for long time or try to connect to database if there is slowness in connecting to database too.
Accepted Solution
Infosys LTD
AU
Hi Guys,
Thanks for your valuable responses actually the issue which we were facing was more over the network side. The link between the Darabase and tye storage was a 1 GBPS link and as we have shared database amoung applications we were pumping more than that hence clogging the storage link. Due to this the data retrieval use to take lot of time. We have now migrated the storage link from 1 GB to 10 GB on the network layer and things are moving faster than ever before.
But, still at some points we do see a sudden hike on the link from average load of 1.5 GB to 4 GB. We are still hunting for that heavy operation which should be causing this. We have taken few reports like AWR, ASH reports from DB. If anyone can lend additional hand on this it would be great.
Thanks a lot everyone.!!!