IBM Lotus Domino 8.5.2 XPages discussion database server performance

This article reports on the performance of IBM® Lotus® Domino® 8.5.2 XPages. A discussion database application workload was used to compare the classic Lotus Domino elements with the XPages design elements.

Christopher Johnson (chrisdjo@us.ibm.com), Performance Engineer, IBM

Christopher Johnson is a member of the IBM Lotus Domino Performance team, with primary focus on NotesBench and Rational tool development. You can reach him at chrisdjo@us.ibm.com. He tested and wrote testing scripts for Rational Performance tester.



Wu W Huang, Software Engineer, IBM

Wu W Huang is a member of the Lotus Domino Performance team, with primary focus iNotes and XPages on Windows and IBM Lotus Domino performance on System Z . You can reach Wu Huang at wuhuang@us.ibm.com. He tested performance of the Classic and XPages discussion database.



07 October 2010

Also available in Russian

Editor's note: Know a lot about this topic? Want to share your expertise? Participate in the IBM Lotus software wiki program today.

Introduction

XPages performance was one of the top priorities for Lotus Domino 8.5.2 server. XPages provides the ability to easily create a web 2.0 user experience in existing Lotus Domino web applications. We used the discussion database that was available with classic Lotus Domino design elements and with XPages design elements (available since Lotus Domino 8.5) to optimize the XPages runtime and design elements. The classic discussion application database scaled up to 200 concurrent users. The new and improved XPages discussion database on Lotus Domino 8.5.2 scaled to three times more concurrent users and total pages per second than the classic discussion database.

The measurements shown in this article use IBM Rational® Performance Tester version 8.1 with the Lotus Domino 8.5.2 server using the classic discussion database and XPages discussion database. Rational Performance Tester simulated Internet users that were performing or browsing common operations using a single Lotus Domino server. Each user performed the following sequence of operations:

  1. Log in.
  2. View all documents.
    • Read five documents.
    • Respond to a document.
  3. View by category.
    • Read five more documents.
  4. Create a topic.
  5. Do a search.
    • Read a document after the search.
  6. Log out.

Hardware and Lotus Domino server configurations

Hardware configuration

The Lotus Domino server was configured on an Intel X5450 server with four processors running Microsoft® Windows® 2003 Enterprise Edition in 64-bit mode. The system was configured with 8 GB memory and one local disk drive. The network used a 1.0 Gbps Ethernet adapter. See table 1.

Table 1. Hardware configuration
ModelIntel X5450
Processors for test / speed4 processors at 3.0 Ghz
Memory8 GB
Active physical drives 1 local disk
Active logical volumesNone
Operating systemMicrosoft Windows 2003 Enterprise Edition, SP2 using 64-bit mode

Lotus Domino configuration

The discussion database contains 113,000 documents and 23 categories and has full text index enabled. The classic discussion database size was 270 MB with template discussion7.ntf from Lotus Domino 7.0, and the XPages discussion database was 700 MB with template discussion8.ntf from Lotus Domino 8.5.2. A single Lotus Domino server 8.5.2 was used to test and compare the performance of the classic and the XPages discussion databases. We did not enable Lotus Domino transaction logging for this comparison. See table 2.

Table 2. Software configuration
DatabaseDetails
XPages discussion databaseDiscussion8.ntf from Lotus Domino 8.5.2
Classic discussion databaseDiscussion7.ntf from Lotus Domino 7.0
Notes.ini settings in addition to those commonly used for these testsHTTPJVMMaxHeapSizeSet=1

Performance test results

Figures 1-4 show the classic discussion database on Lotus Domino 8.5.2 and the XPages discussion database on the Lotus Domino 8.5.2. Each interval shows the average of the one-hour steady state of each incremental set of concurrent users.

Figure 1 shows the percent processor busy and total pages/second (TPS). The processor utilizations were was about the same between the classic and the XPages discussion data bases until 200 users. The XPages discussion database was able to scale up to 500 users with 15 total pages per second, where the classic was able to scale up to only 200 users with 5.5 TPS. For both set of tests one second was used as the acceptable user response time.

Figure 1. Windows: Percent processor busy and total pages/second by number of users
Windows 64: Percent processor busy and total pages/second by number of users

Figure 2 shows the total disk I/O operations per second at different simulated user loads. The classic discussion database showed fewer IOPs for the 200 users supported with response times less than one second.

Figure 2. Windows: Total disk kBytes transferred per second by number of users
Windows 64: Total disk kBytes transferred per second by number of users

Figure 3 shows the total disk kilobytes transferred per second at different simulated user loads.

Figure 3. Windows: Network kBytes per second by number of users
Windows 64: Network kBytes per second by number of users

Figure 4 shows the network kilobytes per second at different simulated user loads. The classic discussion database used two times more network bandwidth than the XPages discussion database because the classic discussion database does not have support for GZIP encoding, while the XPages discussion application has code that does GZIP compression.

Figure 4. Windows: Processor busy and total pages per second with response time of less than three seconds by number of users
Windows 64: Processor busy and total pages per second with response time of less than three seconds by number of users

Figure 4 shows the classic discussion database and the XPages discussion database on Lotus Domino 8.5.2 with user response times of less than three seconds. As shown in figure 4, beyond 500 concurrent users, the XPages discussion application shows a nonlinear increase in processor utilization and a higher response time. This change can be attributed to the database semaphore contention caused by several hundreds of users trying to access a single application. Performance analysis conducted at that load indicates that the XPages runtime itself did not limit the scaling of concurrent users on this application.


Conclusion

The performance of the XPages discussion application has improved in Lotus Domino 8.5.2. User scalability improved three times, and network bandwidth and user throughput (transactions per second) improved. The size of the discussion database increased because of the new features and the new discussion database template supported by XPages.


Appendix

Explanation of Notes.ini settings
Notes.Ini parameter nameExplanation
HTTPJVMMaxHeapSizeSetHTTPJVMMaxHeapSizeSet=1 to prevent the server from resetting the HTTPJVMHeapSize ini back to 64 M from 256 M

Resources

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into IBM collaboration and social software on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Lotus
ArticleID=549566
ArticleTitle=IBM Lotus Domino 8.5.2 XPages discussion database server performance
publish-date=10072010