1 Benchmark Testing Results: OpenText Monitoring and Records Management Running on SQL Server 2012 Running OpenText Monitoring and Records Management on Microsoft SQL Server 2012 provides excellent performance and scalability Technical White Paper Published: July 2012 Applies to: Microsoft SQL Server 2012 Abstract In February 2012, OpenText and Microsoft conducted performance and scalability testing on the Monitoring and Records Management components of the OpenText ECM offering running on Microsoft SQL Server 2012 data-management software. The benchmark testing was very successful, with a peak ingestion of 995,000 messages in a single hour, 14.8 million messages in a 24-hour period, and 171 messages per second up to 15 times the typical ingestion volume. This white paper presents the details of the benchmark testing and the additional benefits that SQL Server 2012 brings to the OpenText ECM Monitoring and Records Management components confirming that SQL Server 2012 is an excellent choice for OpenText Monitoring and Records Management solutions. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server 2012 i
2 2012 Microsoft Corporation. All rights reserved. This document is provided as-is. Information and views expressed in this document, including URL and other Internet website references, may change without notice. You bear the risk of using it. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server 2012 ii
3 Table of Contents Introduction... 1 Introducing the OpenText Monitoring and Records Management Functionality... 2 Benefits of SQL Server Benchmark Testing Overview... 3 Test Environment Details Monitoring Process... 6 Server Configurations... 6 Content Server Configuration... 6 Archive Server Configuration... 7 Search and Index Server Configuration... 8 Database Server Configuration... 8 Test Data Set Benchmark Testing Results Initial Data Set Construction Records Management and Distributed Agents Concurrent Ingestion and Disposition Resource Usage Summary Conclusion Additional Information About OpenText About Microsoft Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server 2012 iii
4 Introduction has transformed the way that companies do business. Yet despite its unparalleled utility, the potential for mismanagement of , paired with its rampant and often insurmountable growth, can make it a staggering liability for corporations. messages and attachments can represent business records that organizations must retain and manage securely to support regulatory compliance, avoid legal fines or litigation costs, and satisfy auditing requirements. It is predicted that the number of regulations governing along with the sheer number of s transmitted throughout organizations will continue to increase. Organizations need a solution for capturing, managing the lifecycle, and streamlining discovery processes for all regulated communications. OpenText is one of our premier contentmanagement partners, and together we are delivering solutions that enable organizations to use business information to achieve strategic advantage. I expect that OpenText will continue to play an important role in our product development efforts aimed at creating new content-management technologies that will help our customers optimize business processes, reduce costs, and utilize information in increasingly powerful ways. Steve Ballmer Chief Executive Officer Microsoft By furthering our close collaboration, OpenText and Microsoft are creating a new dynamic in the marketplace and raising the bar for effective Enterprise Information Management in major industries such as utilities, oil and gas, government, financial services, and legal. In each case, we re demonstrating the power of combining productivity applications from Microsoft with information governance solutions and industry-specific ECM expertise from OpenText. Our relationship with Microsoft is a critical part of our strategy and we will continue to be a leader in delivering new solutions for our joint customers. Mark Barrenechea Chief Executive Officer OpenText The OpenText Monitoring solution helps organizations archive, retrieve, and classify all content that is sent or received by specific accounts within an organization, helping to ensure that the complete range of electronic communications of specific users and groups is fully archived and auditable. OpenText Monitoring and other OpenText applications are built on a sharedservices foundation, which provides a common integration layer and access to content that originates from other systems such as , enterprise resource planning (ERP), file system, and productivity applications, such as Microsoft SharePoint. OpenText and Microsoft work together to deliver solutions that extend the Microsoft platform, including Microsoft Office, SharePoint, Microsoft Exchange, Windows Azure, and Microsoft SQL Server, with industry-specific content applications, combining the power of SQL Server with OpenText s deep understanding of information governance and business-process management. Running OpenText solutions on SQL Server helps organizations scale their database operations with confidence and improve IT and developer efficiency all at a lower total cost of ownership (TCO) than competitive solutions. In February 2012, OpenText and Microsoft conducted performance and scalability testing on the monitoring and records management components of the OpenText ECM offering running on the SQL Server 2012 data-management software. This white paper details the results of this benchmark testing and provides links for further information. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
5 Introducing the OpenText Monitoring and Records Management Functionality OpenText helps customers address challenges related to their information to gain better business insight, to create a positive business impact, to increase process velocity, to reduce risks related to information governance, and to address information security concerns. The OpenText ECM offerings, including Monitoring and Records Management, let organizations easily and rapidly access relevant content and leverage it to create business value without compromising their compliance and security needs. The key benefit of the OpenText Monitoring solution is to manage incoming and outgoing messages; more importantly, the OpenText Monitoring solution effectively classifies the messages and provides defensible disposition of those messages immediately when required. The system therefore needs to remain available while ingesting and defensibly deleting high volumes of content. For more information about OpenText ECM offerings, visit Benefits of SQL Server 2012 SQL Server 2012 is a comprehensive, integrated, and enterprise-ready data-management software solution. It provides a reliable, cost-effective, low-maintenance database framework for OpenText that can support the largest and most process-intensive deployments. Hundreds of enterprises are currently running 10 terabyte (TB) and larger transactional databases on SQL Server. Running OpenText Monitoring and Records Management functionality on SQL Server 2012 provides customers with many benefits: Six nines ( percent) uptime availability for SQL Server 2012 SQL Server customers can protect their mission-critical databases from downtime and data loss with six nines uptime availability. 1,2 Faster to deploy On average, SQL Server database administrators (DBAs) can install and configure new database servers in 1.5 hours, while the largest competitor s DBAs can take 6 hours. 3 Lower hardware cost SQL Server can run on standard commodity server hardware, which can dramatically lower the TCO for customers Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
6 Lower software costs The list price of SQL Server is a third of the largest competitors cost; 4 in addition, SQL Server includes major database-related features, such as high availability; remote disaster recovery; partitioning; data compression; transparent data encryption; spatial; master data management; complex event processing; extract, transform, and load (ETL); online analytical processing (OLAP); data mining; reporting services; and self-service business intelligence (BI) tools. Competitors licensing models add costs for options and add-ins. 5 Simpler systems management and lower staffing costs SQL Server database administrators can typically manage four times as many physical databases as a competitor s DBAs, leading to an estimated annual savings of $5,779 in administrative costs per database, a 460 percent difference in annual cost of administration per database. 6,7 Most secure of any of the major database platforms Since 2002, SQL Server has recorded the fewest reported vulnerabilities as compiled by the National Institute of Standards and Technology (NIST). 8 With SQL Server, OpenText customers can save with reduced licensing, hardware, administration, and support fees, which translate into substantially lower costs over the life of the system. For more information about SQL Server 2012, visit Benchmark Testing Overview As part of their strategic alliance, OpenText and Microsoft ran real-world benchmarking tests at the Microsoft Enterprise Engineering Center (EEC) in Redmond, Washington. The EEC is dedicated to strategic partnerships with industry leaders such as OpenText, providing the hardware, software, and services required by Microsoft customers and product groups to build and validate end-to-end solutions. The benchmarking tests were designed to evaluate the performance and scalability of the Monitoring 10.2 and Records Management 10.2 components of the OpenText ECM offering running on SQL Server The benchmark tests measured the peak ingestion of messages, in addition to the throughput when ingestion and dispositions of messages were running concurrently, a typical real-world use scenario Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
7 Test Environment Details The test environment consisted of 26 servers of varying configuration, all running the Windows Server 2008 R2 Enterprise operating system. The core server environment consisted of a database server running SQL Server 2012, a server running the Archive Server component of the OpenText ECM offering, a search and index server, a server running the Content Server component of the OpenText ECM offering, two servers running Microsoft Exchange Server, and 10 journal servers. Additionally, 10 journal test client servers were used to generate more than 150 million s, simulating the load of a large production environment. Details of the servers are listed in Table 1. Table 1. Servers used in benchmark testing Server Journal test clients Number used 10 Make/model (CPU speed) HP ProLiant DL380 G5 (2.66 GHz) Number of cores per server RAM Additional notes 4 16 GB 20 GB free disk space Servers running Exchange Server 2 HP ProLiant DL580 G GB Eight 256 GB data stores Journal bridge servers 10 HP ProLiant DL380 G6 (2.13 GHz) 8 48 GB 80 journal services Server running Content Server Server running Archive Server 1 IBM System x GB 1 HP ProLiant DL580 G GB Intel Hyper-Threading (HT) Technology enabled 1.8 TB database 10 TB 200 GB database Database server running SQL Server 1 NEC Express5800/A1080a GB 2 TB database 15 TB storage Intel HT Technology enabled Search/index server 1 HP ProLiant DL980 G7 (2.6 GHz) GB 1 TB index Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
8 Figure 1 shows the benchmark testing configuration. Journal Test Clients Journal Bridge Servers Content Server Search/Index Server Servers Running Microsoft Exchange Server Archive Server SQL Server Figure 1. Benchmark testing configuration Table 2 shows details of the software used. Note that all required software updates were applied. Table 2. Software versions used in benchmark testing Server Journal test clients Software OpenText test client Microsoft Outlook 2012 Servers running Exchange Server Exchange Server 2012 Journal bridge servers Server hosting Content Server and search/index server Server hosting Archive Server Database server running SQL Server OpenText Journaling Bridge for Microsoft Exchange Microsoft Outlook 2010 OpenText Content Server with modules: o Classifications o Content Archiving o Management o Records Management o Security Clearance o Search Engine 10.0 OpenText Archive Server OpenText Runtime and Core Services OpenText Archive Services OpenText Administration Client Apache Tomcat with Java SE 6 SQL Server 2012 Release Candidate 0 (RC0) Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
9 Monitoring Process In the monitoring process used for the benchmarking tests, the journal test client servers ran a custom service that checked the number of messages in a journal mailbox on Exchange Server and generated additional journal s if the number fell below a configurable threshold. This let the journal test clients simulate a production environment while only generating as much as can be ingested. Each journal test client server ran eight test client services (total of 80 test client services). The two servers running Exchange Server were configured with four mailbox stores each (total of eight mailbox stores). The 80 journal mailboxes were spread across the mailbox stores (10 mailboxes per store). The journal bridge servers read from their journal mailboxes and then sent the body of the s to Archive Server and the meta-data to Content Server. Each journal bridge server was configured with eight journal services, each reading mail from a separate journal mailbox. Each journal service ran eight worker threads (total of 640 journal service worker threads). These worker threads took a block of s from the inbox and moved them into a sub-folder for processing. For each processed, a journal worker thread first made a request to Content Server to see if another copy of the had been stored previously, then stored the body of the message in Archive Server and stored the meta-data in Content Server. Each of the journal mailboxes for a given test and bridge server was stored in a separate mailbox store, so that the journal test clients and the journal bridges distributed load across the Exchange Server mailbox stores and Content Server. This configuration ensures that the failure of a single journal test client did not dramatically affect the load that could be delivered for the test. Server Configurations This section describes in more detail some of the server configurations used in the benchmark testing. Content Server Configuration Content Server is typically a CPU-intensive and memory-intensive application, and the number of threads it needs is typically the main focus of tuning. To alleviate memory bottlenecks and provide the ability to support larger numbers of CPUs, a Non-Uniform Memory Architecture (NUMA) was used, with multiple connected memory controllers and CPUs and with memory spread across them. The server used to host the Content Server front end included eight of the Intel Xeon processor E processors. Each of these was a 10-core processor with a 30 MB cache and an integrated memory controller, resulting in an 8-node NUMA configuration with a total of 80 cores (160 logical processors with Intel Hyper-Theading *HT+ Technology enabled). Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
10 For the benchmark tests, it was found that the best performance was obtained by running eight instances of Content Server 2010: one for each NUMA node (each node is a set of CPUs and memory connected to a memory controller and cache). Each Content Server instance was configured so that it would be scheduled on a separate NUMA node. Archive Server Configuration For large-scale deployments of Archive Server such as the benchmark testing, OpenText recommends using the concurrent mark-sweep collector 9 and increasing the initial and maximum memory pools from their default values. Following are the Java Virtual Machine (JVM) configuration settings used it the benchmarking tests: In the Java Options box, set: -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSIncrementalPacing -Dorg.apache.commons.logging.Log=com.opentext.ecm. components.logging.wrappers.jclbootlogger -Drcs.console.loglevel=WARN In the Initial memory pool box, specify 256 MB. In the Maximum memory pool box, specify 1024 MB. In the benchmarking tests, there were 10 journal servers, each running eight journal services. Each journal service was configured with eight worker threads (total of 640 journal service worker threads). The journal worker threads alternated between requests to Content Server and requests to Archive Server, so not all of the threads had active Archive Server requests at any given time. Records Management 10.2 uses distributed agent infrastructure of Content Server to perform disposition actions. Each of the eight Content Server front-end instances was configured with 64 distributed agent worker threads (total of 512 distributed agent worker threads). There could therefore be up to 512 connections from Content Server to Archive Server when performing disposition actions. The data flow on the search and index server was configured with 120 extractor threads. Each of these could connect to Archive Server to retrieve s for indexing at any given time. To accommodate the number of clients, the number of connector threads in the Apache Tomcat server hosting Archive Server was increased from the default (200) to 1,024 in the Tomcat server.xml file. 9 A detailed description of the operation of this garbage collector can be found in Memory Management in the Java HotSpot Virtual Machine at https://java.sun.com/j2se/reference/whitepapers/memorymanagement_whitepaper.pdf Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
11 Finally, to accommodate the large number of Tomcat connector threads, the default number of database connections (20 connections) was increased to the maximum (120 connections). Search and Index Server Configuration The search and index server uses the following processes: extraction, extractor merges, document conversion, document conversion merges, update distributor merge, and update distribution. To accommodate the expected ingestion rate, it was anticipated that approximately 120 extractors would be needed. After extraction, 15 merge processes each read input from eight extractors and fed the input into one of 15 document conversion processes. Finally, the output of the document conversion processes was merged before it was sent to the update distributor. The merge processes between the extractors and the document conversion processes had no trouble keeping up with the volume of messages. However, the default configuration of the merge processes between the document conversion processes and the update distributor was tuned to handle the large volume of messages generated by 120 extractors. Content Server on the search and index server was configured for 128 threads to handle the 120 extractors, in addition to administrative requests. Database Server Configuration This section describes the SQL Server 2012 configuration used in the benchmark testing. Maximum memory configuration was set to 480 GB. SQL Server 2012 can dynamically manage memory without administrator intervention. While in most cases this is adequate, servers that host large databases with heavy user traffic might need some limits on memory usage to prevent performance degradation. If the size of the database (actual data space used) is significantly greater than the amount of RAM on the database server, conflicting demands on the memory can develop over time. SQL Server 2012 can continue growing its in-memory data cache to avoid reading from disk, but the operating system might push back, trying to allocate memory for itself and other processes. The result can be excessive memory paging and a negative effect on performance. For this reason, the maximum memory configuration was set to 480 GB. For more information, see Max degree of parallelism was set to 8. The SQL Server 2012 configuration option max degree of parallelism controls the number of processors used for the execution of a query with a parallel plan. This option determines the computing and thread resources used for the query plan operators that can perform the work in parallel. There are several factors that affect the "max degree of parallelism" setting, including the number of processors used, if Intel HT Technology is enabled or not, and whether the server has NUMA configured. For the benchmark testing, the "max degree of parallelism" was set to 8. For more information, see Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
12 TempDB was created with one data file per core. The configuration of the SQL Server tempdb database is critical to the performance of SQL Server. In the benchmark testing, tempdb was created with one data file per server core (for a total of 80 files), with each file set to the same size. This enabled the proportional fill algorithm to distribute the allocation load uniformly with minimal contention. For more information, see Locked pages in memory privilege was granted to the SQL Server service account so that large memory pages could be used. Applications based on Windows can use Address Windowing Extensions (Windows AWE) APIs to allocate and to map physical memory into the process address space. Memory that is allocated by using this method is never paged out by the operating system and is locked down until the application explicitly frees it or exits. The use of Windows AWE APIs for memory management is also frequently referred to as "locked pages." The "locked pages in memory" user right for the startup account on the instance of SQL Server in Windows Server was granted so that SQL Server could use large memory pages. For more information, see SE_MANAGE_VOLUME_NAME right was granted to the SQL Server service account to permit instant file initialization. Data and log files are initialized to overwrite any existing data left on the disk from previously deleted files. Data and log files are first initialized by filling the files with zeros when, for example, a database is created or when files, logs, or data files are added to an existing database. In SQL Server 2012, data files can be initialized instantaneously. This allows for fast execution of these file operations. Instant file initialization reclaims used disk space without filling that space with zeros; instead, disk content is overwritten as new data is written to the files. In the benchmark testing, the SQL Server service account was granted SE_MANAGE_VOLUME_NAME (members of the Windows Administrator group have this right and can grant it to other users by adding them to the Perform Volume Maintenance Tasks security policy). This allowed for instant file initialization when creating or expanding data files. For more information, see RSS Queues were set to a maximum of 8, and the RSS base CPU was set to 16. Receive-Side Scaling (RSS) improves the ability of Windows Server to handle heavy network traffic. To maximize SQL Server throughout in the benchmark testing, RSS Queues (MaxNumRssCpus) were set to the maximum of 8, and the RSS base CPU was set to 16. For more information, see /maximizing-sql-server-throughput-with-rss-tuning.aspx. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
13 Test Data Set The data set used was the Enron Data Set, the largest and richest set of publically available, general-purpose corporate to date. This data set was publicly released as part of Federal Energy Regulatory Commission (FERC) Western Energy Markets investigation, was converted to industry-standard formats by Electronic Discovery Reference Model (EDRM), and consists of 1,227,255 s with 493,384 attachments covering 151 custodians. 10 Benchmark Testing Results Results obtained from the benchmarking tests include observations from the initial period of building up the data set, from isolated tests of Records Management 10.2 on the distributed agent framework, and from testing concurrent ingestion and disposition of s, representing a realworld usage scenario. Initial Data Set Construction Figure 2 shows the peak ingestion rate obtained during the period used to build up the data set for running disposition tests. Note that during the test period, the journal bridge servers were configured so as not to ingest between 1:00 and 5:00 A.M. to correspond to the Exchange Server maintenance window. Additionally, the journal services and Content Server instances were stopped between 6:00 and 7:00 A.M. to collect logs. Figure 2. Peak ingestion rate (ingestion only) 10 Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
14 These results show that OpenText Monitoring is able to ingest very high volumes of and to sustain high ingestion rates over a 24-hour period. During the 24-hour period, the software ingested a total 14.8 million s (roughly 10 to 15 times what existing customers typically ingest) and was able to sustain ingestion of more than 600,000 s for each full hour of ingestion. Records Management and Distributed Agents The disposition processing in Records Management 10.2 takes advantage of the distributed agent infrastructure available in Content Server The distributed agent framework spreads the work of a set of independent tasks among multiple worker-agent threads. For many agent processes, the distributed agent infrastructure allows a significant increase in throughput compared to a singlethreaded agent process. To determine if the distributed agent infrastructure is able to handle the high volume requirements of Records Management dispositions, a test task was created to generate distributed agent tasks with the action none. These tasks perform all the usual steps of a disposition action but do not action the item. Table 3 shows the results of this test on a set of 581,470 objects with 16 distributed agent worker threads and performing no action. Table 3. Disposition performance (with action: none) Metric Result Worker threads 16 Action None Result set size 581,470 Disposition search time 0:00:40 Disposition action time 0:18:03 Extrapolated search throughput Extrapolated action throughput 872,205 s/minute 46,388,742 s/day These results show that Records Management 10.2 is able to return more than 580,000 results from a disposition search in 40 seconds. They also show that Records Management 10.2 is able to perform all the task and Records Management overhead for the actions in 18 minutes. These metrics represent a search rate of approximately 872,000 results per minute and an action rate of more than 46 million s per day confirming that the Content Server distributed agent infrastructure running on SQL Server 2012 is able to keep up with even the most demanding Records Management environments. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
15 Concurrent Ingestion and Disposition Concurrent ingestion and disposition represents the real-world scenario of an operational OpenText Monitoring system using Records Management to dispose of that does not need to be retained. Table 4 shows the result of performing a disposition search and action on approximately 8.65 million s concurrent with ingestion. Table 4. Concurrent disposition performance (with action: destroy) Metric Result Worker threads 512 Action Destroy Result set size 8,650,429 Disposition search time 0:10:38 Disposition action time 1:00:54:40 Extrapolated search throughput Extrapolated action throughput 813,520 s/minute 8,344,044 s/day These results show that Records Management 10.2 is able to return more than 8.6 million results from a disposition search in less than 11 minutes and is able to destroy those items in slightly less than 25 hours. These results represent a search rate of more than 813,000 results per minute and an action rate of 8.3 million s per day. Figure 3 shows ingestion rates achieved while performing the disposition actions. Figure 3. Peak ingestion rate (concurrent ingestion) Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
16 These results show that OpenText Monitoring 10.2 is able to maintain very high ingestion rates, even while processing disposition actions. Overall, Records Management was able to destroy 8.65 million s in the same period that the bridge servers ingested another 7.2 million s confirming that Records Management 10.2 is able to keep up with even the busiest monitoring environments. Resource Usage Resource-usage results were obtained by running the system performance report from Windows Performance Monitor on each of the servers. Overall, the resource usage on the servers shows that hardware was not a significant bottleneck during the benchmarking tests; the results of the tests therefore demonstrate the maximum throughput of the software. Table 5 shows the resource overview from Content Server during the concurrent test. Table 5. Resource use for server hosting OpenText Content Server Component Status Utilization Details CPU Normal 23 percent Normal CPU load Network Normal 16 percent Disk Idle 86 per second Busiest network adapter is between 15 percent and 60 percent Disk input/output (I/O) is less than 100 read/write per second on disk 0 Memory Normal 32 percent 89,712 MB available Table 6 shows the resource overview from Archive Server host during the concurrent test. Table 6. Resource use for server hosting OpenText Archive Server Component Status Utilization Details CPU Idle 6 percent Low CPU load Network Idle 1 percent Busiest network adapter is less than 15 percent Disk Normal 409 per second Disk I/O is between 100 and 500 read/write per second on disk 2 Memory Normal 30 percent 44,643 MB available Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
17 Table 7 shows the resource overview from the server hosting Exchange Server during the concurrent test. Table 7. Resource use for server hosting Microsoft Exchange Server Component Status Utilization Details CPU Idle 13 percent Low CPU load Network Idle 1 percent Busiest network adapter is less than 15 percent Disk Normal 119 per second Disk I/O is between 100 and 500 read/write per second on disk 7 Memory Normal 54 percent 60,845 MB available These results show that the hardware used to host the Content Server front-end instances, the Archive Server instance, and Exchange Server proved more than sufficient to execute on the tasks required. Table 8 shows the resource overview from the database server hosting SQL Server during the concurrent test. Table 8. Resource use for server hosting Microsoft SQL Server Component Status Utilization Details CPU Idle 14 percent Low CPU load Network Normal 16 percent Disk Busy 1,699 per second Busiest network adapter is between 15 percent and 60 percent Disk I/O is more than 500 read/write per second on disk 1 Memory Busy 94 percent 33,594 MB available While these results show that both memory use and disk I/O were high on the SQL Server host during the tests, the higher disk I/O was observed during index rebuilds, so disk I/O is not believed to have had an impact on the tests. Summary The benchmark testing results were impressive, with a peak ingestion of 995,000 messages in a single hour, 14.8 million messages in a 24-hour period, or 171 messages per second. These throughputs show that the OpenText ECM offering, when supported by the SQL Server 2012 datamanagement software, can support a massive number of concurrent transactions. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
18 Throughput (msg/sec) Table 9 shows highlights of the benchmark testing results. Table 9. Highlights of benchmark testing results Metric Peak ingestion Concurrent dispositions and ingestion Description 171 messages/second 995,000 messages/hour 14.8 million messages in 24 hours 82 messages/second sustained ingestion 96 messages/second sustained disposition 7.1 million messages ingested and 8.3 million messages destroyed in 24 hours Figure 4 shows the sustained throughput for a 24-hour period in messages per second Stand-alone Ingestion Concurrent Destruction Figure 4. Sustained throughput for 24 hours (in messages/second) A typical message-ingestion volume for large organizations is between 1 and 1.5 million messages per day; the benchmark testing results are up to 15 times higher. In addition, a typical -disposition rate for large organizations is approximately 170,000 per 24- hour period; the test results from this study are 48 times higher. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
19 Conclusion OpenText and Microsoft ran real-world benchmarking tests to evaluate the performance and scalability of the Monitoring and Records Management components of the OpenText ECM offering running on SQL Server The tests measured the peak ingestion of messages, in addition to the throughput when ingestion and dispositions of messages were running concurrently. The results showed that the OpenText solutions, when supported by the SQL Server 2012 database platform, can support extremely high numbers of concurrent transactions, ingesting and dispositioning at rates that satisfy the most demanding environments. The benchmark testing confirms that the Monitoring and Records Management components of the OpenText ECM offering running on SQL Server 2012 can provide performance and scalability to meet the needs of even the largest enterprise customers. OpenText customers can select SQL Server 2012 for their database platform with confidence, and can be assured that their requirements can be easily met with OpenText Monitoring and Records Management. Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
20 Additional Information The following references provide more information about OpenText and Microsoft. About OpenText OpenText, an enterprise software company and leader in enterprise content management, helps organizations manage and gain the true value of their business content. OpenText brings two decades of expertise supporting millions of users in 114 countries. Working with customers and partners, OpenText brings together leading content experts to help organizations capture and preserve corporate memory, increase brand equity, automate processes, mitigate risk, manage compliance, and improve competitiveness. For more information about OpenText products and services, visit About Microsoft Founded in 1975, Microsoft (Nasdaq MSFT ) is the worldwide leader in software, services, and solutions that help people and businesses realize their full potential. For more information about Microsoft products and services, visit Benchmark Testing Results: OpenText Monitoring and Records Management and Microsoft SQL Server
Benchmark Testing Results: CSC s Integral Life Insurance Software Running on SQL Server Running CSC s Integral life insurance solution on Microsoft SQL Server and Windows Server provides unmatched performance
Benchmark Testing Results: CSC s Integral Running on SQL Server Running CSC s Integral insurance software suite on Microsoft SQL Server and Windows Server provides unmatched performance and scalability
Dassault Systèmes ENOVIA V6 Running on SQL Server 2008 R2 Enterprise Benchmark testing confirms that ENOVIA V6 is a high performing and scalable system on SQL Server2008 R2 Enterprise and Windows Server
Benchmark Testing Results: Telvent ArcFM Solution Running on Microsoft SQL Server Benchmark testing confirms the superior performance and scalability of Telvent ArcFM Solution 10.0.1 SP1 running on SQL
Benchmark Testing Results: Unparalleled Scalability of Itron Enterprise Edition on SQL Server Benchmark Testing Confirms That Itron Enterprise Edition TM Meter Data Management Can Support 10 Million Meters
Benchmark Testing Results: Teamcenter Running on SQL Server 2012 and Servers Based on Intel Xeon Processors Running Teamcenter from Siemens PLM Software on Microsoft SQL Server 2012 and servers based on
Proven Performance for Accenture Duck Creek Policy Administration Commercial Lines Benchmark testing confirms scalability and performance of Microsoft SQL Server 2012 and servers based on the Intel Xeon
Proven Performance for Accenture Duck Creek Policy Administration Commercial Lines Benchmark testing confirms scalability and performance of Microsoft SQL Server 2012 and servers based on the Intel Xeon
SQL Server Business Intelligence on HP ProLiant DL785 Server By Ajay Goyal www.scalabilityexperts.com Mike Fitzner Hewlett Packard www.hp.com Recommendations presented in this document should be thoroughly
Microsoft SQL Server 2008 R2 Enterprise Edition and Microsoft SharePoint Server 2010 Better Together Writer: Bill Baer, Technical Product Manager, SharePoint Product Group Technical Reviewers: Steve Peschka,
Estimate Performance and Capacity Requirements for Workflow in SharePoint Server 2010 This document is provided as-is. Information and views expressed in this document, including URL and other Internet
Microsoft Analytics Platform System Solution Brief Contents 4 Introduction 4 Microsoft Analytics Platform System 5 Enterprise-ready Big Data 7 Next-generation performance at scale 10 Engineered for optimal
Uniting the Business and Petrotechnical Worlds Addressing the challenges of E&P through a unified, familiar, and open petrotechnical computing environment that promotes collaboration, accelerates integrated
Kronos Workforce Central 6.1 with Microsoft SQL Server: Performance and Scalability for the Enterprise Providing Enterprise-Class Performance and Scalability and Driving Lower Customer Total Cost of Ownership
Technical white paper HP ProLiant BL660c Gen9 and Microsoft SQL Server 2014 technical brief Scale-up your Microsoft SQL Server environment to new heights Table of contents Executive summary... 2 Introduction...
Benchmark Testing Results: TEMENOS T24 Running on Microsoft SQL Server 2012 High-water benchmark testing confirms the performance and scalability of TEMENOS T24 R12 running on SQL Server 2012 and Windows
Server Consolidation with SQL Server 2008 White Paper Published: August 2007 Updated: July 2008 Summary: Microsoft SQL Server 2008 supports multiple options for server consolidation, providing organizations
Express5800 Scalable Enterprise Server Reference Architecture For NEC PCIe SSD Appliance for Microsoft SQL Server An appliance that significantly improves performance of enterprise systems and large-scale
WHITEPAPER Accelerating Enterprise Applications and Reducing TCO with SanDisk ZetaScale Software SanDisk ZetaScale software unlocks the full benefits of flash for In-Memory Compute and NoSQL applications
Configuration and Development BENEFITS Enables powerful performance monitoring. SQL Server 2005 equips Microsoft Dynamics GP administrators with automated and enhanced monitoring tools that ensure 24x7
Published: April 2012 Applies to: SQL Server 2012 Copyright The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.
Database Server Configuration Best Practices for Aras Innovator 10 Aras Innovator 10 Running on SQL Server 2012 Enterprise Edition Contents Executive Summary... 1 Introduction... 2 Overview... 2 Aras Innovator
1 SQL Server 2012 Optimization, Performance Tuning and Troubleshooting 5 Days (SQ-OPT2012-301-EN) Description During this five-day intensive course, students will learn the internal architecture of SQL
Tableau Server 7.0 scalability February 2012 p2 Executive summary In January 2012, we performed scalability tests on Tableau Server to help our customers plan for large deployments. We tested three different
Business white paper HP Process Automation Version 7.0 Server performance Table of contents 3 Summary of results 4 Benchmark profile 5 Benchmark environmant 6 Performance metrics 6 Process throughput 6
Scalability Microsoft Dynamics GP 10.0 Benchmark Performance: Advantages of Microsoft SQL Server 2008 with Compression White Paper May 2009 Contents Introduction... 3 Summary Results... 3 Benchmark Test
Best Practices for Optimizing SQL Server Database Performance with the LSI WarpDrive Acceleration Card Version 1.0 April 2011 DB15-000761-00 Revision History Version and Date Version 1.0, April 2011 Initial
SQL Server Consolidation Using Cisco Unified Computing System and Microsoft Hyper-V White Paper July 2011 Contents Executive Summary... 3 Introduction... 3 Audience and Scope... 4 Today s Challenges...
White paper: Unlocking the potential of load testing to maximise ROI and reduce risk. Executive Summary Load testing can be used in a range of business scenarios to deliver numerous benefits. At its core,
Scaling Database Performance in Azure Results of Microsoft-funded Testing Q1 2015 2015 2014 ScaleArc. All Rights Reserved. 1 Test Goals and Background Info Test Goals and Setup Test goals Microsoft commissioned
Oracle Primavera Contract Management, Business Intelligence Publisher Edition-Sizing Guide An Oracle White Paper July 2011 1 Disclaimer The following is intended to outline our general product direction.
EMC Unified Storage for Microsoft SQL Server 2008 Enabled by EMC CLARiiON and EMC FAST Cache Reference Copyright 2010 EMC Corporation. All rights reserved. Published October, 2010 EMC believes the information
Technical White Paper Report Technical Report Benchmarking Cassandra on Violin Accelerating Cassandra Performance and Reducing Read Latency With Violin Memory Flash-based Storage Arrays Version 1.0 Abstract
WHITE PAPER Improve Business Productivity and User Experience with a SanDisk Powered SQL Server 2014 In-Memory OLTP Database 951 SanDisk Drive, Milpitas, CA 95035 www.sandisk.com Table of Contents Executive
White Paper EMC XtremSF: Delivering Next Generation Storage Performance for SQL Server Abstract This white paper addresses the challenges currently facing business executives to store and process the growing
Performance Analysis of Web based Applications on Single and Multi Core Servers Gitika Khare, Diptikant Pathy, Alpana Rajan, Alok Jain, Anil Rawat Raja Ramanna Centre for Advanced Technology Department
Cognos Performance Troubleshooting Presenters James Salmon Marketing Manager James.Salmon@budgetingsolutions.co.uk Andy Ellis Senior BI Consultant Andy.Ellis@budgetingsolutions.co.uk Want to ask a question?
Page 1 of 10 Quick Links Home Worldwide Search Microsoft.com for: Go : Home Product Information How to Buy Editions Learning Downloads Support Partners Technologies Solutions Community Previous Versions
MakeMyTrip CUSTOMER SUCCESS STORY MakeMyTrip is the leading travel site in India that is running two ClustrixDB clusters as multi-master in two regions. It removed single point of failure. MakeMyTrip frequently
White Paper Dell Microsoft Business Intelligence and Data Warehousing Reference Configuration Performance Results Phase III Performance of Microsoft SQL Server 2008 BI and D/W Solutions on Dell PowerEdge
WHITE PAPER HP ProLiant DL580 Gen8 and HP LE PCIe Workload WHITE PAPER Accelerator 90TB Microsoft SQL Server Data Warehouse Fast Track Reference Architecture Based on Microsoft SQL Server 2014 Data Warehouse
MS Exchange Server Acceleration Maximizing Users in a Virtualized Environment with Flash-Powered Consolidation Allon Cohen, PhD OCZ Technology Group Introduction Microsoft (MS) Exchange Server is one of
SQL Server 2012 Parallel Data Warehouse Solution Brief Published February 22, 2013 Contents Introduction... 1 Microsoft Platform: Windows Server and SQL Server... 2 SQL Server 2012 Parallel Data Warehouse...
white paper Capacity and Scaling of Microsoft Terminal Server on the Unisys ES7000/600 Unisys Systems & Technology Modeling and Measurement 2 This technical white paper has been written for IT professionals
JVM Performance Study Comparing Oracle HotSpot and Azul Zing Using Apache Cassandra January 2014 Legal Notices Apache Cassandra, Spark and Solr and their respective logos are trademarks or registered trademarks
SQL Server 2014 What s New? Christopher Speer Technology Solution Specialist (SQL Server, BizTalk Server, Power BI, Azure) email@example.com The evolution of the Microsoft data platform What s New
ESG Lab Summary Hyper-V R2 SP1 Application Workload Performance Virtualizing SQL Server, SharePoint, and Exchange with Confidence This report presents a summary of Microsoft-commissioned testing of the
Oracle Primavera P6 Enterprise Project Portfolio Management Performance and Sizing Guide An Oracle White Paper October 2010 Disclaimer The following is intended to outline our general product direction.
Information Management ILM et Archivage Les solutions IBM Dr. Christian ARNOUX Consultant Information Management IBM Suisse, Software Group 2007 IBM Corporation IBM Strategy for Enterprise Content Compliance
WITH A FUSION POWERED SQL SERVER 2014 IN-MEMORY OLTP DATABASE 1 W W W. F U S I ON I O.COM Table of Contents Table of Contents... 2 Executive Summary... 3 Introduction: In-Memory Meets iomemory... 4 What
Dell Virtualization Solution for Microsoft SQL Server 2012 using PowerEdge R820 This white paper discusses the SQL server workload consolidation capabilities of Dell PowerEdge R820 using Virtualization.
Achieving Nanosecond Latency Between Applications with IPC Shared Memory Messaging In some markets and scenarios where competitive advantage is all about speed, speed is measured in micro- and even nano-seconds.
EMC Perspective Integrated Grid Solutions from SAS, EMC Isilon and Greenplum Introduction Intensifying competitive pressure and vast growth in the capabilities of analytic computing platforms are driving
IBM SPSS Statistics Server Understanding the Benefits of IBM SPSS Statistics Server Contents: 1 Introduction 2 Performance 101: Understanding the drivers of better performance 3 Why performance is faster
DEPLOYING VIRTUALIZED MICROSOFT DYNAMICS AX 2012 R2 EMC Solutions Abstract This document describes the reference architecture of a virtualized Microsoft Dynamics AX 2012 R2 implementation that is enabled
Oracle BI EE Implementation on Netezza Prepared by SureShot Strategies, Inc. The goal of this paper is to give an insight to Netezza architecture and implementation experience to strategize Oracle BI EE
High performance ETL Benchmark Author: Dhananjay Patil Organization: Evaltech, Inc. Evaltech Research Group, Data Warehousing Practice. Date: 07/02/04 Email: firstname.lastname@example.org Abstract: The IBM server iseries
Online Transaction Processing in SQL Server 2008 White Paper Published: August 2007 Updated: July 2008 Summary: Microsoft SQL Server 2008 provides a database platform that is optimized for today s applications,
SYSTEM X SERVERS SOLUTION BRIEF Maximum performance, minimal risk for data warehousing Microsoft Data Warehouse Fast Track for SQL Server 2014 on System x3850 X6 (95TB) The rapid growth of technology has
Benchmark Results for Temenos T24 with SQL Server 2008 R2 on Intel-based NEC Servers 25 Million Highwater Benchmark Testing Proves Performance and Scalability Contents: Abstract...1 A Brief Introduction
HP SN1000E 16 Gb Fibre Channel HBA Evaluation Evaluation report prepared under contract with Emulex Executive Summary The computing industry is experiencing an increasing demand for storage performance
ORACLE DATABASE 10G ENTERPRISE EDITION OVERVIEW Oracle Database 10g Enterprise Edition is ideal for enterprises that ENTERPRISE EDITION For enterprises of any size For databases up to 8 Exabytes in size.
Performance benefit of MAX5 for databases The MAX5 Advantage: Clients Benefit running Microsoft SQL Server Data Warehouse (Workloads) on IBM BladeCenter HX5 with IBM MAX5 Vinay Kulkarni Kent Swalin IBM
Introduction 1 Performance on Hosted Server 1 Figure 1: Real World Performance 1 Benchmarks 2 System configuration used for benchmarks 2 Figure 2a: New tickets per minute on E5440 processors 3 Figure 2b:
Case Study: Load Testing and Tuning to Improve SharePoint Website Performance Abstract: Initial load tests revealed that the capacity of a customized Microsoft Office SharePoint Server (MOSS) website cluster
hp availability stats and performance software network and system monitoring for hp NonStop servers a product description from hp features at a glance Online monitoring of object status and performance
Performance brief for IBM WebSphere Application Server.0 with VMware ESX.0 on HP ProLiant DL0 G server Table of contents Executive summary... WebSphere test configuration... Server information... WebSphere
WHITE PAPER FUJITSU PRIMERGY AND PRIMEPOWER SERVERS Performance Comparison of Fujitsu PRIMERGY and PRIMEPOWER Servers CHALLENGE Replace a Fujitsu PRIMEPOWER 2500 partition with a lower cost solution that
White Paper Capacity Planning Guide for Adobe LiveCycle Data Services 2.6 Create applications that can deliver thousands of messages per second to thousands of end users simultaneously Table of contents
WHITE PAPER Affordable, Scalable, Reliable OLTP in a Cloud and Big Data World: IBM DB2 purescale Sponsored by: IBM Carl W. Olofson December 2014 IN THIS WHITE PAPER This white paper discusses the concept
ENZO UNIFIED SOLVES THE CHALLENGES OF OUT-OF-BAND SQL SERVER PROCESSING Enzo Unified Extends SQL Server to Simplify Application Design and Reduce ETL Processing CHALLENGES SQL Server does not scale out
W H I T E P A P E R Microsoft SQL Server on Stratus ftserver Systems Security, scalability and reliability at its best Uptime that approaches six nines Significant cost savings for your business Only from
Cloud Based Application Architectures using Smart Computing How to Use this Guide Joyent Smart Technology represents a sophisticated evolution in cloud computing infrastructure. Most cloud computing products
SAP HANA - Main Memory Technology: A Challenge for Development of Business Applications Jürgen Primsch, SAP AG July 2011 Why In-Memory? Information at the Speed of Thought Imagine access to business data,
Microsoft Virtualization: Data Center to Desktop Customer Solution Case Study IT Firm Virtualizes Databases: Trims Servers 85 Percent, Ups Performance 50 Percent Overview Country or Region: United States
Performance Tuning and Optimizing SQL Databases 2016 http://www.homnick.com email@example.com +1.561.988.0567 Boca Raton, Fl USA About this course This four-day instructor-led course provides students
Intelligent Business Operations and Big Data 1 What is Big Data? Big data is a popular term used to acknowledge the exponential growth, availability and use of information in the data-rich landscape of
DELL s Oracle Database Advisor Underlying Methodology A Dell Technical White Paper Database Solutions Engineering By Roger Lopez Phani MV Dell Product Group January 2010 THIS WHITE PAPER IS FOR INFORMATIONAL
Performance and scalability of a large OLTP workload ii Performance and scalability of a large OLTP workload Contents Performance and scalability of a large OLTP workload with DB2 9 for System z on Linux..............
White Paper Optimizing the Performance Of MySQL Cluster Table of Contents Introduction and Background Information... 2 Optimal Applications for MySQL Cluster... 3 Identifying the Performance Issues.....
Executive Summary Maximizing Your Server Memory and Storage Investments with Windows Server 2012 R2 October 21, 2014 What s inside Windows Server 2012 fully leverages today s computing, network, and storage
Accelerate SQL Server 2014 AlwaysOn Availability Groups with Seagate Nytro Flash Accelerator Cards Technology Paper Authored by: Mark Pokorny, Database Engineer, Seagate Overview SQL Server 2014 provides
- Analyzer 2007 Executive Summary Strategy Companion s Analyzer 2007 is enterprise Business Intelligence (BI) software that is designed and engineered to scale to the requirements of large global deployments.
SQLstream Blaze and Apache Storm A BENCHMARK COMPARISON 2 The V of Big Data Velocity means both how fast data is being produced and how fast the data must be processed to meet demand. Gartner The emergence