Overview of the Best Practices for Content Manager System Performance

Abstract

This technote provides an overview of the best practices for Content Manager system performance, including performance methodology, and checklists.

For related information about this topic, refer to the following IBM Redbooks publication:
Performance Tuning for Content Manager, SG24-6949-01

Contents

The Content Manager best practices performance methodology and checklists are based on some of the most common applicable performance tuning recommendations from the Content Manager Performance Team at the Silicon Valley Lab and services practitioners in the field. Although not all the platforms and databases are covered here, many of the principals and methodologies are applicable across platforms and databases.

The best practices performance methodology over the life cycle of a Content Manager system is shown in the diagram below. We recommend following the recommended tasks during your initial system planning, installation, and configuration. If you have not done so during the initial rollout of your system, it is possible to implement them at a later time.

The tasks are Plan for performance sizing, Design and configure, Tune O/S, Effective disk I/O, Tune DB2, Tune WebSphere Application Server, Tune Tivoli Storage Manager, Optimize database, Routine maintenance, and Monitoring
After the initial installation, implementing routine maintenance and monitoring can start the performance tuning process again. This practice helps to ensure that your Content Manager system is always being tuned for performance and to ensure that the user community is not affected by performance problems.

AIX

The following is a checklist of the steps to be implemented for a successful Content Manager system implementation in an AIX environment:
(
Bold text contains best practices steps that are common to all the platforms. For details of these steps, refer to the companion IBM Redbook,
Performance Tuning for Content Manager, SG24-6949-01.)

  • Plan for performance.
  • Design and configure for performance.
  • Adjust maximum number of processes.
  • Use JFS2 and EJFS for logical volumes and file systems.
  • Configure ulimit values for DB2 instance owners.
  • Set all machines to full duplex.
  • Set MTU size to maximum supported by LAN.
  • Configure effective disk I/O usage.
  • Spread DB components over multiple disks.
  • Create separate instances during installation.
  • Set default database location.
  • Set default database log location.
  • Initial parameter tuning for Library Server database.
  • Increase default buffer pool if more than 1 GB RAM.
  • WebSphere Application Server: Tune Java heap size.
  • Tune Tivoli Storage Manager buffer pool size.
  • Initial index configuration: Use runstats/rebind.
  • Regular maintenance: Use snapshots.
  • Regular maintenance: Use runstats/rebind.
  • Regular maintenance: Reorgch/reorg.

Linux

The following is a checklist of the steps to be implemented for a successful Content Manager system implementation in a Linux environment:

  • Plan for performance.
  • Design and configure for performance.
  • Set limits.
  • Configure shared memory.
  • Configure semaphores.
  • Configure message queues.
  • Tune network.
  • Tune file systems for external storage.
  • Configure effective disk I/O usage.
  • Spread DB components over multiple disks.
  • Create separate instances during installation.
  • Configure default database location.
  • Change database log location.
  • WebSphere Application Server: Configure Java heap size.
  • Configure Tivoli Storage Manager buffer pool size.
  • Initial index configuration: Use runstats/rebind.
  • Regular maintenance: Use snapshots.
  • Regular maintenance: Use runstats/rebind.
  • Regular maintenance: Use reorgch/reorg.

Windows

The following is a checklist of the steps to be implemented for a successful Content Manager system implementation in a Windows environment:

  • Plan for performance.
  • Design and configure for performance.
  • Disable Indexing service.
  • Disable computer browser service.
  • Disable Internet information service.
  • Disable 8.3 file name creation service.
  • Check memory.
  • Tune network.
  • Set boot.ini parameters.
  • Configure effective disk I/O usage.
  • Spread DB components over multiple disks.
  • Create separate instances during installation.
  • Change default database location.
  • Change default database log location.
  • WebSphere Application Server: Configure Java heap size.
  • Tune Tivoli Storage Manager buffer pool size.
  • Initial index configuration: Use runstats/rebind.
  • Regular maintenance: Use snapshots.
  • Regular maintenance: Use runstats/rebind.
  • Regular maintenance: Use reorgch/reorg.

Maintenance

After a Content Manager system has been designed, installed, and configured, it is important to perform maintenance tasks regularly. This ensures that you get the best possible performance from your system over time, as well as potentially avoid problems that can manifest themselves as system-endangering situations.

We recommend performing the following list of the maintenance steps on a scheduled basis:

  • Optimize server databases using runstats/rebind.
  • Optimize server databases using reorgchk.
  • Monitor LBOSDATA directory size.
  • Manage staging directory space.
  • Remove entries from the events table.
  • Remove log files.
  • Manage Resource Manager utilities and services.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment. publib-b.boulder.ibm.com

Profile

Publish Date
11 August 2006


Rating: Not yet rated


Author(s)

IBM Form Number
TIPS0636