Performance Constraints

Portal Server performance can be CPU bound, memory bound or even bound by the capability of the garbage collector. The scenario where the portal is CPU bound is the easiest to detect and resolve. If CPU utilization at the point of peak load is greater than 75% the deployment will benefit from additional CPUs. Portal scales well to servers with 4 CPUs and it scales linearly when adding additional servers so long as the network itself is not an issue. Even if at the time of deployment a Portal Server installation is neither CPU nor memory bound a successful portal induces stickiness and the load increases over time. Consequently as with any web application it is paramount to monitor CPU, memory and all other logs consistently.