IBM Daeja ViewONE Virtual Performance and Scalability

Size: px

Start display at page:

Download "IBM Daeja ViewONE Virtual Performance and Scalability"

Preston Cameron
6 years ago
Views:

1 Summary White Paper January 2016 IBM Daeja ViewONE Virtual Performance and Scalability Copyright IBM Corporation 2016 Enterprise Content Management No part of this document may be reproduced in any form by any means without prior written authorization of IBM This document is provided as is without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranty of merchantability or fitness for a particular purpose. This document is intended for informational purposes only. It could include technical inaccuracies or typographical errors. The information herein and any conclusions drawn from it are subject to change without notice. Many factors have contributed to the results described herein and IBM does not guarantee comparable results. Performance numbers will vary greatly depending upon system configuration. All data in this document pertains only to the specific test configuration and specific releases of the software describe.

2 Introduction IBM Daeja ViewONE provides web-based image viewers that extend your web browser. You can use these viewers to view, annotate, zoom, magnify, scroll, pan, rotate, and print your images and image documents quickly and easily. IBM Daeja ViewONE Virtual is a server-based document and image viewer that provides a lightweight HTML and JavaScript front end for users of mobile devices or desktops. Most processing takes place on the server, which makes the viewer ideal for use where a client Java environment is not permitted or supported. Therefore, you can use IBM Daeja ViewONE Virtual to provide a lightweight front end for users of mobile devices or desktops where a JRE is not supported. This paper presents scalability information for IBM Daeja ViewONE Virtual. Assessments of response times for selected system functions and processor utilization for the servers are given independently as a way of characterizing overall system performance. Both the vertical and horizontal scalability characteristics of IBM Daeja ViewONE Virtual were tested with a workload that models a realistic mix of the most common transactions. Vertical scalability tests used a single Daeja server to measure the system processor utilization under workload incensement. Horizontal scalability tests used a cluster of Daeja servers, to measure the system processor utilization and load balancing of the cluster under proportional workload. Both of the vertical and horizontal scalability tests demonstrated good scalability with throughput under a load of 110 TPM (Transaction Per Minute) with a few seconds response time for the operations tested. Our tests also showed balanced workload across the three Daeja nodes of the cluster environment. The performance results reported present data and workloads run on an isolated network on specific operating environments and system configurations. Actual performance in real customer environments with production workloads may vary depending on many factors such as system configurations, workload characteristics, document type and size. The results presented here are not guaranteed to be repeatable in other systems. Page 2 of 9

3 Test Overview Control Environment The test environment is within an isolated network. Each component of the Daeja cluster environment was configured as a physical machine with dedicated resources. Daeja server Load Generator Intel Xeon CPU (2 processors, 12 cores), 64GB RAM Intel Xeon CPU (2 processors), 8GB RAM Windows 2012R2, WebSphere Network Deployment , Java SDK 1.7 Windows 2012R2, Rational Performance Tester Figure 1 Environment Figure 2 Environment topology Test Matrix The test aimed to simulate a realistic customer scenario, a typical test document set was selected to cover how most common files appear in the real life. The files selected were Microsoft Word/Excel/PPT, JPEG, TIF and PDF files and with sizes ranging from 32KB to 22MB. The test used all types of documents; some of the complex documents took a longer time to respond, thus, even with a lower Page 3 of 9

4 workload, the average of response time still took a few seconds. These documents were stored in the Daeja server side. When the viewer is launched, users can simply select the file to view, or select other operations. File type Percentage Size range Microsoft Word 23% 32kb ~ 2,788kb Microsoft Excel 27% 32kb ~ 448kb Microsoft PowerPoint 9% 1,200kb ~ 1,700kb JPEG Image 5% 5,000kb ~ 6,000kb TIF Image 14% 1,200kb ~ 1,760kb PDF files 23% 100kb ~ 22,000kb Figure 3 Test document table In this test, the workload was driven by the IBM Rational Performance Tester (RPT) test tool. The mix workload is made up of three common operations, including document viewing, printing and redaction, with an overall ratio of 70% viewing, 20% printing and 10% redaction. Test Results Performance and scalability are measured by response times, processor utilization, and throughput. Scalability is the capability of a system to handle resources proportionally in response of increasing workload. A system that scales well should show a near-linear throughput increase against the system resources usage while maintaining or even increasing its level of the performance or efficiency when tested in a larger operational demand. Scaling vertically means to add resources to a single node in a system, in this case a single IBM Daeja server, typically the addition of CPUs or RAM to a single machine. Vertical Scalability Figure 4 shows the Response time and CPU usage of the Daeja server under increasing workload. The CPU usage of the server increased proportionally with increased load; and for the Response time, we saw a good scaling up to about 110 transactions per minute and 60% CPU utilization for this document mix that includes some large and complex documents. We also monitored the Disk bytes/sec (sum of reads/writes) and Network interface bytes/sec (sum of sent/received) in figure 5, and they showed a linear growing alone with the CPU usage. Page 4 of 9

5 Bytes/sec CPU utilization Response time (sec) CPU utilization Response time and CPU utilization Mix operations View Print Redact CPU utilization % 25 90% 80% 20 70% 60% 15 50% 10 40% 30% 5 20% 10% 0 0% Transaction Per Minute Figure 4 Response time and CPU utilization with TPM Disk/Network transaction and CPU utilization Disk Bytes/sec Network Bytes/sec CPU utilization 30,000,000 25,000,000 20,000,000 15,000,000 10,000,000 5,000, % 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Transaction Per Minute Figure 5 Disk/ Network transaction data and CPU Utilization Page 5 of 9

6 CPU utilization Horizontal Scalability To test horizontal (or scale out) scalability, means to add identical Daeja server machines, to make a load balanced cluster of 3 Daeja servers. In our case, the cluster uses WebSphere Application Server Network Deployment. Figure 6 showed the CPU utilization of all Daeja servers in the system with single workload (1X), doubled workloads (2X) and tripled workloads (3X). The IBM Daeja servers have good balanced CPU usage. Response times remain flat while throughput nearly doubled and tripled with the second and third Daeja server, from 45 TPM to 126 TPM. Horizontial CPU Utilization 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Node 1 Node 2 Node % 17.65% 17.69% 17.77% 17.18% 17.64% 1X 2X 3X Workloads Figure 6 CPU Utilization with different workloads Page 6 of 9

7 Response time (ms) Transaction per minute Response time and TPM View Mix operations Print Redact Transaction Per Minute 10, ,000 8,000 7, ,000 5,000 4, ,000 2,000 1, X 2X 3X 0 Workload Figure 7 Transaction Per Minute with different workloads Conclusion The vertical and horizontal scalability tests demonstrated that IBM Daeja ViewONE Virtual can be configured to handle additional workload vertically by adding more power (e.g. CPU, RAM) to our existing machine or horizontally by adding more physical machines into your pool of resources (Daeja server instances). Page 7 of 9

8 Monitoring & Tuning CPU/Disk To determine the optimal configuration for the bulk import process, monitor the CPU, memory, and disk utilization. Depending upon the operating system, nmon or perfmon can be used to monitor the server statistics and help identify areas for tuning. Daeja ViewONE process monitoring and troubleshooting The Daeja ViewONE Knowledge Center references multiple options for monitoring and troubleshooting the bulk import process. More information on the IBM Daeja ViewONE Virtual can be found in IBM Knowledge Center- Daeja ViewONE You can also get help from Getting fixes from Fix Central Contacting IBM Software Support Best Practices and Tuning Recommendations When deploying Daeja ViewONE into IBM WebSphere ND (Network Deployment), you need to configure the following: Java JVM Machine: in a 32bit machine, the heap size limits to 1800mb, and there is no limitation for 64bit machine. We typically set the Initial heap size to equal or to slightly less than the maximum heap size. In that way, it will allocate maximum memory at startup, eliminate memory allocating during test and reduce unnecessary garbage collection. We also suggest setting the new area size (nursery size) as a half of the initial heap size and using the gencon policy. For the test run for this paper, we set both the heap sizes to 4,096mb and 2048mb as the nursery size (-Xmn2048m) and used gencon (Xgcpolicy:gencon) as the garbage collection policy. Recommend to configure the web container size depending on the number of concurrent user requests in your environment. Monitor the thread pool utilization and adjust it as needed for your workload. For the test we ran for this paper, in Thread pools > WebContainer, set minimum size and maximum to 100. If you are running a horizontal cluster, the memory-to-memory sharing setting is needed: In the WebSphere console, navigate to Server types > WebSphere application servers > <cluster node name> > Session management > Distributed environment settings, select Memory-tomemory replication, this specifies how session data is saved in a distributed environment. Page 8 of 9

9 Author Hongzhen Wang, ECM QA Engineering Thanks to these contributors who helped improve this paper Dave Royer, ECM Performance Engineering Architect Daeja ViewONE SVT team in Dublin Daeja ViewONE Development team in UK Page 9 of 9

... IBM AIX performance and tuning tips for Oracle s JD Edwards EnterpriseOne web server

... IBM AIX performance and tuning tips for Oracle s JD Edwards EnterpriseOne web server IBM AIX performance and tuning tips for Oracle s JD Edwards EnterpriseOne web server Applies to JD Edwards EnterpriseOne 9.0 with tools release 8.98 or 9.1........ Diane Webster IBM Oracle International