Sun Microsystems Portal Server 6 - Manual (Page 64)

Portal Sizing
64 Portal Server 6 2005Q1 • Deployment Planning Guide
Establish Baseline Sizing Figures
Once you have identified your business and technical requirements, and mapped
Portal Server features to your needs, your sizing requirements emerge as you plan
your overall Portal Server deployment. Your design decisions help you make
accurate estimates regarding Portal Server user sessions and concurrency.
Your Sun Java System technical representative can provide you with an automated
sizing tool to calculate the estimated number of CPUs your Portal Server
deployment requires. You need to gather the following metrics for input to the
sizing tool:
• Peak Numbers
• Average Time Between Page Requests
• Concurrent Users
• Average Session Time
• Search Engine Factors
Other performance metrics that affect the number of CPUs a Portal Server
deployment requires, but are not used by the sizing tool, are:
• Portal Desktop Configuration
• Hardware and Applications
• Back-end Servers
• Transaction Time
• Workload Conditions
A discussion of the these performance factors follows.
Peak Numbers
Maximum number of concurrent sessions defines how many connected users a Portal
Server deployment can handle.
To calculate the maximum number of concurrent sessions, use this formula:
NOTE Sizing requirements for a secure portal deployment using Sun Java
System Portal Server Secure Remote Access (SRA) software are
covered in
“SRA Sizing” on page 72 .