Lotus Domino Server R5 Implementation Guide

June 18, 2001

 

 

Distribute I/O Across Physical Disks

Our experience has shown that physical and logical disk structures are our customers' least understood system resource, and the one most often undersized. The best way to boost performance on many Domino servers is to distribute I/O across separate physical disk subsystems.

Ideally, you want to put the following I/O-intensive files on separate physical disks:

ŸThe Notes paging file

ŸYour .NSF files

ŸThe Domino R5 transaction log

If you can put them on separate controllers, too, so much the better. The idea is to increase I/O throughput by distributing the work over busses, controllers, ports, and disks. Hence, several small physical disks are better than a few large-capacity disks. In particular, the more you isolate the R5 transaction log from other disk activity, the better your server performance will be.

Log Performance Metrics Consistently

If you don't log performance metrics, you won't be able to quantify the success or failure of your tuning efforts. If you do keep logs, you'll not only have a far better idea of what you're doing, you'll have a far easier time documenting the need for additional expenditures.

Among the key metrics to track are:

ŸTotal CPU utilization (expressed as a percentage). If this metric is above 70% to 80%, that's a red flag.

ŸDisk queue length (typically this should be less than 2 items in the queue) and average disk service time (should be less than 70%).

ŸPaging file size and utilization. Utilization should be fairly low, or it's probably worth it to buy more memory

ŸDomino statistics and events for mail throughput, replication, Web server activity, and database activity.

ŸDomino logs (log.nsf); they're boring but they often come in handy.

It's important to collect production data weekly, and analyze it monthly if possible. It's also critical to capture "snapshots" of performance before and after major configuration changes.

For AIX systems, there is a Notes Agent for Performance Toolbox (PTX) that will monitor and report on Domino Performance.

Optimize for Domino R5

Domino R5 does a great job auto-configuring and dynamically reconfiguring key parameters for maximum performance. Here are some tips from the experts on how to tune the Domino R5 server itself:

ŸSet up the correct number of mailboxes. Multiple mail.box files reduce contention for mail deposits and other mail-related activity. The biggest performance gains come when you add a second mailbox. The rule of thumb we use is one mailbox for 1-200 users supported, two or more for 200-1,000 and ten (the maximum) for 1,000 or more users.

ŸFor non-partitioned systems, let Domino dynamically set NSF_Buffer_Pool_Size. This is particularly important in low memory server configurations, where a large buffer pool can interfere with the kernel's memory management.

Page 9

Page 9
Image 9
IBM manual Distribute I/O Across Physical Disks, Log Performance Metrics Consistently, Optimize for Domino R5

R5 specifications

IBM R5, also known as IBM Notes R5, marked a significant evolution in the IBM Notes and Domino platform, offering users enhanced capabilities and features that improved productivity and collaboration in the workplace. Released in 1999, R5 introduced a more refined user interface, improved performance, and a range of new tools designed to facilitate communication and teamwork.

One of the standout features of IBM R5 was its comprehensive integration of email, calendaring, and tasks within a single interface. This centralized approach allowed users to manage their communications more efficiently, reducing the need to switch between multiple applications. The improved email functionality included enhanced filtering and sorting capabilities, enabling users to better organize their inboxes.

The R5 version also introduced significant advancements in the collaborative aspects of the platform. With new tools for team collaboration, such as enhanced discussion databases and a shared documents feature, R5 made it easier for teams to work together on projects irrespective of their physical locations. The introduction of instant messaging capabilities further bridged communication gaps, allowing users to connect in real time.

IBM R5 was built on a robust architecture that incorporated Domino server enhancements, which improved scalability and performance. The platform supported new technologies, including Java applets, allowing developers to build more dynamic and interactive applications. Additionally, the integration of the LDAP (Lightweight Directory Access Protocol) provided better directory services, making it simpler to manage user identities across the network.

Security features were also a focus in R5, with improvements in encryption and user authentication that helped safeguard sensitive data. The platform’s ability to integrate with other enterprise applications while maintaining robust security protocols made it a choice for organizations that prioritized data protection.

Moreover, IBM R5 incorporated a more modular and flexible architecture, enabling easier customization and management of applications and components. This adaptability catered to a wide range of business needs, thus positioning IBM Notes R5 as a versatile solution for organizations looking to enhance their workflow and communication processes.

Overall, IBM R5 served as a milestone in the evolution of enterprise collaboration solutions. Its innovative features, user-friendly interface, and robust security measures laid the foundation for future developments in the IBM Notes and Domino ecosystem, ultimately contributing to more efficient and effective business practices.