Hello Zimkhita
Actually I found same problem in some SSM systems, specially one we implemented with 160 KPIs.How many KPIs are you trying to display in your scorecard?
Some hints to tune the performance of your box:
- Adjust JVM parameters in NWA. If you have a server with 32GB, you can define a heap size of 8192 MB. Thats in NWA->Configuration->Java System Parameters-> JVM Paramenters
- Check table CPMS_PAS_VARS (I don't remember the exact name). There is one parameter in which you define the cache for PAS calls.
- I have no access to SSM system right now, but I think that in lsdal.ini or lsserver.ini you can define some memory parameter.
- Check with Internet Explorer Developer Tools (F12) --> Network -> Start Capturing the trace to SSM calls when you open the SSM or when you change the context. You will some how one of the calls may take 60 seconds to complete. At the same time you can go to the NWA logs and check for the pip call and check if is the PIP call taking some much or any other issue.
Our biggest issue is that a PAS model with 660 KPIs (=3300 measures) and one year data is working slower. If for any scorecard you try to retrieve many KPIs it takes also more time. I'm afraid that PAS is not designed for supporting medium-high data volume scenarios...
The last option I would like to check, is to test the partition of the PAS model (last time I saw an option in PAS Admin). And other option would be to use more than one PAS model for same SSM implementation...
Let's see if you can improve the performance of your SSM.