Report Received from developer : Performance is poor when navigating through developer portal. Opening different tabs etc.
Reviewed alert logs for that specific user and noticed lot of PEGA0001 with high KPI Over thresholds.
Noticed earlier PEGA0037 and added fua/enableAssemblyAvoidance setting to true ..
Specific to PEGA0001 analysis - noticed always PxOtherIOElapsed is contributing to the overall delay . Per PDN / Help - pxOtherIOElapsed is - Elapsed time accessing non-rule-resolved instances from database -- Basically all data/work related entries. .
DB Trace showed iterative DB calls less than the PEGA0005 threshold makes sense on why there is no 0005 alert . But , There is some performance hit here and there is no alert set for this ...
Why this was not added in to RDBIOElapsed as it is aggregate of RDB operations. ? What is causing the performance hit here ? Why may be a same query is executed in multiple iterations. Any thoughts and insight will be good to know...
***Updated by moderator: Lochan to add SR Exists group tag***
This means that you don't have a single long running SQL that is responsible for the db time elapsed and that's why you don't see Pega0005. To identify the SQLs behind pxOtherIO Elapsed, temporarily reduce the threshold of 0005 alerts and then track these SQLs down.
Thank you .. Yes, I was able to track that using DB trace .. It is multiple queries that is collectively accounting for pxOtherIOElapsed and alert is PEGA0001. It would be more meaningful if ti is accounted on RDBIO or different alert. Still investigating ..