Establishing an appropriate sizing estimate for your Portal Server deployment is an iterative process. You might wish to change the inputs to generate a range of sizing results. Customizing your Portal Server deployment can greatly affect its performance.
After you have an estimate of your sizing, consider:
Use the following LDAP transaction numbers for an out-of-the-box portal deployment to understand the impact of the service demand on the LDAP master and replicas. These numbers change once you begin customizing the system.
Access to authless anonymous portal - 0 ops
Login by using the Login channel - 2 BINDS, 2 SRCH
Removing a channel from the Portal Desktop - 8 SRCH, 2 MOD
Reloading the Portal Desktop - 0 ops
One of the primary uses of Portal Server installed on an application server is to integrate portal providers with Enterprise JavaBeansTM architecture and other J2EETM technology stack constructs, such as Java Database Connectivity (JDBCTM) and J2EETM Connector Architecture (JCA), running on the application server. These other applications and modules can consume resources and affect your portal sizing.