Domino 6 for z/OS - Considerations for Improved Performance

Published 20 May 2003, updated 21 May 2003

Authors: Mike Ebbers


This hint and tip lists and explains important basic steps you should keep in mind for improving performance in Domino 6 on zSeries.


The performance of Domino on zSeries is an important topic, but sometimes the basics steps of performance tuning are overlooked. Following are our key recommendations for performance tuning, performance monitoring, and capacity planning of Lotus Domino Release 6 for z/OS.

Monitor z/OS closely as you introduce Domino
Domino does not run the same way as other zSeries workloads that you may be used to. Make sure that you are not artificially constraining Domino with parameter settings designed for a different type of application.

Use a team approach
Domino tuning on zSeries is a combination of:

  • z/OS tuning, including z/OS UNIX System Services tuning
  • Domino server tuning
  • DASD tuning
  • Network tuning
Therefore, the Domino administrator, the z/OS and z/OS UNIX System Services performance specialists, the DASD administrator, and the network administrator must work together to optimize Domino performance.

Consult our list of tuning recommendations
Tuning recommendations are provided at the beginning of each chapter in the redbook SG24-6904.

Use valid measurements for capacity planning
Avoid using simple single-function tests as an indicator of the capacity of zSeries as a Domino server. These tests are easy to run, but can give very misleading results.

Instead, valid capacity planning approaches are discussed in Chapter 8, “Capacity planning and performance management” in the redbook SG24-6904. This redbook will help you to understand what tests generally are valid, what to measure, and how to interpret the measurements. It can help you to avoid reaching invalid conclusions about the true power of Lotus Domino Release 6 for z/OS on the zSeries hardware platform

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.

Follow IBM Redbooks

Follow IBM Redbooks