C H A P T E R 2

Performance Tuning

This section provides tuning suggestions to assist you in obtaining the best performance from your Content Delivery Server system.

This section presents the following topics:

Tuning Configuration Variables

Tuning the Oracle Database

Tuning the Application Server

2.1 Tuning Configuration Variables

Configuration variables are used for the database connection pool size, memory settings, and database memory allocations. The values set for these variables can affect the performance of your system.

This section provides some guidelines for setting the configuration variables to improve performance.

2.1.1 Set the Database Connection Pool Size

The Content Delivery Server uses two connection pools, one for the Catalog Manager schema and one for the Vending Manager schema. If there is more than one Vending Manager, each Vending Manager schema has its own connection pool. The Catalog Manager and Developer Portal share a connection pool. The Vending Manager, Fulfillment Manager, Subscriber Portal, Event Service, Postpaid Service, and Report Service share a connection pool. If the Event Service is deployed with only a Catalog Manager, the Event Service shares the Catalog Manager's pool.

The maximum number of database connections allowed for a pool is determined by the first application that is loaded. Therefore, specify the same number of database connections for each component that shares a connection pool. For optimal performance, set the number of database connections as described in the following guidelines.

In the following files, set the db.pool.size.max property to eight times the number of CPUs on the server on which the Content Delivery Server is running. For example, if the server has two CPUs, set this property to 16.

$CDS_HOME/deployment/deployment-name/conf/SubscriberPortal.properties

$CDS_HOME/deployment/deployment-name/conf/VSAdminConsole.properties

$CDS_HOME/deployment/deployment-name/conf/FulfillmentService.properties

$CDS_HOME/deployment/deployment-name/conf/EventService.properties

$CDS_HOME/deployment/deployment-name/conf/PostpaidService.properties

$CDS_HOME/deployment/deployment-name/conf/ReportService.properties

In the following files, set the db.pool.size.max property to two times the number of CPUs on the server on which the Content Delivery Server is running. For example, if the server has two CPUs, set this property to 4.

$CDS_HOME/deployment/deployment-name/conf/AdminConsole.properties

$CDS_HOME/deployment/deployment-name/conf/DeveloperPortal.properties

Each database used for the Content Delivery Server schemas must be configured to support the number of connections specified for each schema. Set the sessions parameter for the database to a number greater than the sum of connections specified. For example, using the sample numbers given in the guidelines and assuming that the Catalog Manager and one Vending Manager share a database, set the sessions parameter to at least 20.

Note - If the server on which the database is running cannot support the number of connections specified and performance is degraded, reduce the connection pool sizes as needed to avoid overloading the database.

Changes take effect when the Content Delivery Server is restarted.

2.1.2 Set the Memory Settings

If you are using WebLogic Server and you deployed all components to the same server, Content Delivery Server works well with 50% of a host's memory assigned to the Java virtual machine. Reduce this value if the host is running database or other resource-intensive processes.

1. Edit the $CDS_HOME/deployment/deployment-name/bin/start_server.sh file.

2. Modify the statement export JAVA_MEM="-ms1024m -mx1024m" and set each value to half the size of system memory.

Changes take effect when the Content Delivery Server is restarted.

Tip - Change the java.mem property in the deployment configuration file that you use to deploy Content Delivery Server. Updating the configuration file ensures that the desired values are used for future deployments.

2.1.3 Set the Database Memory Allocations

The optimal database configuration is dependent on many factors. Use the information provided in this section as a starting point for your database management and tuning.

For systems with up to 5000 items of content and 50 devices, use the following guidelines for memory allocation:

Set the shared pool size to 2 gigabytes.

Set the buffer cache to 1.5 gigabytes or larger.

For a shared database configuration, use the following guidelines:

Set the Process Global Area (PGA) target using the following equation:

10 megabytes * the maximum number of database connections

See Section 2.1.1, Set the Database Connection Pool Size for information on database connections.

Set the large pool using the following equation:

200 megabytes + the User Global Area (UGA)

UGA = 0.5 megabytes * the maximum number of database connections. See Section 2.1.1, Set the Database Connection Pool Size for information on database connections.

For a dedicated database configuration, use the following guidelines:

Set the Process Global Area (PGA) target using the following equation:

(10 megabytes * the maximum number of database connections) + UGA

UGA = 0.5 megabytes * the maximum number of database connections. See Section 2.1.1, Set the Database Connection Pool Size for information on database connections.

Set the large pool to 200 megabytes.

Set the Java_pool_size parameter to 0.

As more content or devices are added to your system, more memory might be required, especially for the buffer cache. Insufficient memory allocations might result in database error messages or slower performance.

2.2 Tuning the Oracle Database

See the Oracle web site (http://technet.oracle.com) for tips on tuning database performance.

2.3 Tuning the Application Server

Performance might also be improved by tuning your application server.

See the Sun Java System Application Server web site (http://wwws.sun.com/software/sunone/) for tips on tuning Sun Java System Application Server.

See the WebLogic Server web site (http://www.weblogic.com/) for tips on tuning WebLogic Server. Use the WebLogic Server console to set the following parameters as described:

Set the thread count to 30.

Disable dynamic servlet class reloading by setting Reload Period to -1 for each web application.

If you are using WebLogic Server, disable dynamic reloading of web pages created using JavaServer Pages trademark technology by following these steps:

1. Change to the $CDS_HOME/deployment/deployment-name/weblogic/domains/domain-name/applications directory.

2. Edit each of the following files and set the param-name element pageCheckSeconds to -1 as shown in CODE EXAMPLE 2-1.

adminconsole/weblogic.xml

developerportal/weblogic.xml

subscriberconsole/weblogic.xml

vsadmin/weblogic.xml

CODE EXAMPLE 2-1 Update to weblogic.xml

<jsp-descriptor>

  <jsp-param>

    <param-name>pageCheckSeconds</param-name>

    <param-value>-1</param-value>

  </jsp-param>

  <jsp-param>

    <param-name>keepgenerated</param-name>

    <param-value>false</param-value>

  </jsp-param>

</jsp-descriptor>

Changes take effect when the Content Delivery Server is restarted.