oracle fusion middleware capacity planning guide

Oracle Fusion Middleware Capacity Planning Guide Software Configuration Needed

During Oracles internal performance testing, WebLogic Portal was CPU bound, so the performance of the system will depend on how fast each CPU is and how many total CPUs there are.

The capacity planning benchmark data presented in this guide was verified against WebLogic Portal 10.2.

The WebLogic Portal sets the standard for the delivery of enterprise-class portal solutions and is designed to meet the scalability and performance requirements for some of the most demanding deployments.

WebLogic Portal solutions range from departmental applications to some of the largest corporate deployments in existence.

The architecture and physical deployment of any given implementation depends on numerous factors which this document will cover.

Oracle Fusion Middleware Capacity Planning Guide Software Configuration Needed

The process of evaluating the hardware and software configuration needed for a given deployment is called capacity planning.

This document is a guide for developing capacity planning numbers not a prescription or recommendation for any specific deployment.

While designing your solution and testing the configuration, careful consideration must be given to business expectations, periodic fluctuations in demand, and application constraints few deployments are identical.

Customers need to plan carefully, test methodically, and incorporate conservative principles such as deploying with extra capacity not a bare minimum.

Before deploying any application into a production environment the application should be put through a rigorous performance testing cycle.

For more information on performance testing see Approaches to Performance Testing at on the Oracle Technology Network web site.

Any and all recommendations provided in this guide should be adequately verified before a given system is moved into production.

As stated above, the data published in this document is meant to represent the specific configuration that was tested.

There are a number of factors that come into play when determining how much capacity a system can support and thus there is no substitute for adequately testing a prototype to obtain your own capacity planning numbers.

If you do not have a group experienced in physical architecture, capacity planning, performance testing, and disaster recovery planning you should strongly consider getting assistance.

The hardware capacity required to support your application depends on the specifics of the application, server hardware, network infrastructure, and portal configuration.

You should consider how each of these factors applies to your implementation.

Understanding these factors and considering the requirements of your application will aid you in generating server hardware requirements for your configuration.

Before an application is ready to be sized for a production deployment it should go through an iterative performance testing process to ensure that bottlenecks are addressed and that response behaviors meet requirements.

Catching these kinds of problems early will significantly reduce the overhead in trying to fix them later.

Anything that will be included in the production deployment, such as a monitoring tool, load balancer, or intrusion detection software, should be replicated in the testing environment if possible.

Many testing configurations include synthetic network traffic generators to make testing as accurate as possible.

This is the single most important factor when determining how well the system will scale.