When developing Portal applications, there is a inclination to pit lots of functionalities over the portal node. You’ll find simpler ways by which we are in a position to lessen the pressure around the portal node utilizing a couple of of people guidelines:
Avoid running multiple services on one portal node. e.g. Setup Explore another node or serve images inside the server ( might be edge server)
Avoid synchronising session data across portal nodes. Sync user session data using Dynacache is big overhead over the CPU that’s very memory intensive. Use sticky sessions or avoid storing huge data on session
When you use WCM inside the portal node, try and utilize remote rendering rather of local rendering
Try bundling logical portlets inside the same EAR. Allows you to certainly avoid multiple classloaders
Uninstall the portlets that are not used inside the atmosphere. If you are handling the elements using XMLAccess, you may even uninstall the manager portlets
Cache whenever achievable – whether it’s WCM content or portal assets
In situation you deploying newer portal applications – try and utilize Client Side Aggregation (CSA)
Besides a couple of in the aforementioned, another primary explanations why portal node migh receive overloaded is
Login process – Might be taking too extended.
Website Landing Page – lots of portlets, data being retrieved from multiple systems
Caching – to obtain that extra performance, large amount of occasions, we try to get the whole data and cache, to ensure that whenever the customer clicks more or expand, we’re capable of possibly serve within the cache.
Trace logger enabled for that Server
Utilization of heavy styles
Quantity of portlets / page
