Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE Manual
  1. Manuals
  2. Brands
  3. Blackberry Manuals
  4. Server
  5. ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING...
  6. Manual
Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE Manual

Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE Manual

Performance benchmarking for microsoft exchange
Hide thumbs Also See for ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE:
Table of Contents

Advertisement

Quick Links

Download this manual
BlackBerry Enterprise Server for
Microsoft Exchange
Version 4.1
Performance Benchmarking

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE and is the answer not in the manual?

Questions and answers

Related Manuals for Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE

Summary of Contents for Blackberry ENTERPRISE SERVER FOR MICROSOFT EXCHANGE - - PERFORMANCE BENCHMARKING GUIDE

  • Page 1 BlackBerry Enterprise Server for Microsoft Exchange Version 4.1 Performance Benchmarking...
  • Page 2 At the time of publication, this documentation is based on BlackBerry Enterprise Server Version 4.1 for Microsoft Exchange. ©2006 Research In Motion Limited. All Rights Reserved. The BlackBerry and RIM families of related marks, images, and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion, BlackBerry, “Always On, Always Connected” and the “envelope in motion”...
  • Page 3 Research In Motion Limited Research In Motion UK Limited 295 Phillip Street Centrum House, 36 Station Road Waterloo, ON N2L 3W8 Egham, Surrey TW20 9LF Canada United Kingdom Published in Canada...

  • Page 5: Table Of Contents

    Contents Overview ................................9 About this document ............................9 Audience ..............................10 BlackBerry Enterprise Server components ....................11 BlackBerry Dispatcher............................11 BlackBerry Messaging Agent..........................11 MAPI ................................12 CDO ................................12 BlackBerry Router ............................12 BlackBerry Controller ............................12 BlackBerry MDS Services..........................12 BlackBerry MDS Connection Service ......................13 BlackBerry Attachment Service ........................13...
  • Page 6 Load generator computer equipment....................21 Performance testing tools ..........................21 Microsoft Load Simulator 2003......................21 BlackBerry MDS Connection Service Push Load Testing tool ............22 BlackBerry Synchronization Service Load Testing tool ..............22 Measurement counters ..........................22 Lab initialization.............................. 22 Performance tests...............................
  • Page 7 Appendix: MMB and MMB2 comparison ......................51 Overview................................51 BlackBerry Attachment Service traffic for MMB2 ................55 Appendix: BlackBerry MDS Connection Service traffic rate derivation ........... 57 Message test load traffic ..........................57 BlackBerry MDS Connection Service load traffic..................57 Appendix: Calculations and data........................59...

  • Page 9: Overview

    BlackBerry Enterprise Solution™ in a Microsoft Exchange environment. The performance tests that this document describes are based on the ability of the BlackBerry Enterprise Server to support 2000 user accounts. Each test was run for four hours. Research In Motion (RIM) used the data collected in the last two hours of the test, when the load driver reached a steady state load, for analysis.

  • Page 10: Audience

    BlackBerry Enterprise Server for Microsoft ExchangePerformance Benchmarking Audience This document assumes that you have a working knowledge of the following items: • BlackBerry Enterprise Server for Microsoft Exchange installation, configuration, administration, and architecture • Microsoft Exchange Server 2000 and, or 2003 installation and administration •...

  • Page 11: Blackberry Enterprise Server Components

    This mechanism is used to initially synchronize the BlackBerry device and the Microsoft Exchange message store, enabling wireless synchronization to occur. Each BlackBerry Messaging Agent owns a unique internal SRP identifier that connects to the BlackBerry Dispatcher.

  • Page 12: Mapi

    The BlackBerry Router acts as a gateway to the BlackBerry Infrastructure and user computers. It determines whether data should be transmitted wirelessly or routed through a network connection. When a BlackBerry device is connected to a computer, the BlackBerry Router routes data to the BlackBerry device and bypasses the wireless network.

  • Page 13: Blackberry Mds Connection Service

    The BlackBerry MDS Connection Service also communicates with the BlackBerry Dispatcher. It permits persistent socket connections from the BlackBerry device to the corporate application server. You can configure the BlackBerry MDS Connection Service to run on a computer that is remote from the BlackBerry Enterprise Server computer.

  • Page 14: Blackberry Synchronization Service

    BlackBerry device and message store, enabling wireless synchronization to occur. Because the initialization feature is not considered to maintain a steady state load on the BlackBerry Enterprise Server, its impact on the BlackBerry Enterprise Server performance is not included in this document. There are load conditions that the initialization places on the system that you should consider when initialization occurs.

  • Page 15: Blackberry Enterprise Server Implementation Considerations

    BlackBerry users. RIM recommends that you place the BlackBerry Enterprise Server as close to the messaging servers as possible and target the messaging servers that host the majority of BlackBerry users. Depending on the WAN infrastructure, you might want to implement a BlackBerry Enterprise Server in more than one site for optimal performance.

  • Page 16: Blackberry Mds Connection Service Traffic

    When implementing the BlackBerry MDS Connection Service, consider both the rate at which data is sent to BlackBerry devices and the amount of transcoding that the data requires. Do not push too much data that requires transcoding to BlackBerry devices when messaging traffic is heavy; doing so might cause message delivery to slow.

  • Page 17: Wireless Enterprise Activation

    Activating BlackBerry devices wirelessly involves pushing content from a user's mailbox to a BlackBerry device that is not connected to a computer. A large amount of data is sent through the BlackBerry Enterprise Server to the BlackBerry device, which results in increased wireless traffic, increased activity by the BlackBerry Enterprise Server, and increased activity by the messaging and collaboration servers.
  • Page 18 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...

  • Page 19: Test Environment

    The following tables provide information about the various components that RIM used in the performance test environment. In some cases, these components are greater than the minimum requirements established for the BlackBerry Enterprise Server Version 4.1 for Microsoft Exchange. Microsoft Exchange Server equipment...

  • Page 20: Blackberry Enterprise Server Equipment

    Microsoft XML Version 4.0 SP 2 (MSXML) • Java™ 2 Runtime Environment, SE 1.4.2_03 configuration The BlackBerry Enterprise Server was configured with one administrative service account. The service account was given the following permissions for each Microsoft Exchange Server information store: • Send As •...

  • Page 21: Load Generator Computer Equipment

    In their performance tests, RIM used the MAPI Messaging Benchmark 2 (MMB2), which is a workload defined in LoadSim 2000 and has been used in previous benchmarking for the BlackBerry Enterprise Server Version 4.0. RIM used LoadSim 2003 because they selected Microsoft Exchange 2003 for the benchmarking of BlackBerry Enterprise Server 4.1.

  • Page 22: Blackberry Mds Connection Service Push Load Testing Tool

    Using the BlackBerry MDS Connection Service Push Load Testing tool, RIM can specify any URL to push, wait for notification, and enable transcoding. The new tool enables more features of the BlackBerry MDS Connections Service to be exercised.

  • Page 23: Performance Tests

    RIM obtained the performance data through a series of tests that were conducted in a controlled environment. Twenty-five tests were run to determine the impact of the BlackBerry Enterprise Server on the Microsoft Exchange Server 2003. The performance tests also displayed the performance characteristics of the BlackBerry Enterprise Server.
  • Page 24 50% of all attachments were requested from BlackBerry devices • % of messages viewed by Loadsim was adjusted accordingly so • 2000 user accounts on 2 Microsoft Exchange that messages are either only viewed on the BlackBerry device or Servers ® in the Microsoft Outlook client •...
  • Page 25 • 2000 user accounts on 2 Microsoft Exchange • measured the impact of the BlackBerry MDS Collaboration Servers Service load on the BlackBerry Enterprise Server and on the Microsoft SQL Server • 500 BlackBerry user accounts • BlackBerry MDS Connection Service pulled pages equivalent to •...
  • Page 26 2000 user accounts on 2 Microsoft Exchange • measured the impact of all benchmarked BlackBerry features Servers enabled at the same time on the BlackBerry Enterprise Server, Microsoft Exchange Server, and on the Microsoft SQL Server • 500 BlackBerry user accounts •...

  • Page 27: Microsoft Exchange 2003 Performance Test Results

    Microsoft Exchange Servers. The data was averaged across two Microsoft Exchange Servers, each with exactly the same number of Microsoft Exchange and BlackBerry user accounts enabled for all benchmarking scenarios. See “Performance tests” on page 23 for more information about each performance test.

  • Page 28: Processor Use

    The largest impact on the processor occurred when all features were enabled. The processor time increased by 19.81%, which was a 3.65-time increase above the baseline value with no BlackBerry user accounts enabled. Looking at the individual features, enabling wireless email reconciliation along with the core email, calendar, and sent item redirection had the largest impact to Microsoft Exchange with respect to processor time.

  • Page 29: Memory Use

    It is a good measure of the impact on the disk subsystem used by the messaging server as BlackBerry user accounts are enabled with specific features. The configuration for these tests had 6 disks configured as RAID 0 with 15K rpm drives that, on average, can handle over 120 IOPS for each disk.
  • Page 30 Out of the individual features that were benchmarked, RIM observed that wireless email reconciliation, along with the core BlackBerry features enabled (email, calendar, sent item redirection) caused the largest increase in disk use. Disk transfers /sec grew from 77.52 to 335.82, which was a 3.33-time increase in disk transfers /sec. See “Appendix: Calculations and data”...

  • Page 31: Network Use

    For individual features, RIM observed that wireless email reconciliation, along with the core BlackBerry features enabled (email, calendar, sent item redirection), caused the largest increase in network use. The network bytes / sec grew from 0.68 Mbps to 3.13 Mbps, which was a 3.6-time increase from the baseline value without BlackBerry user accounts enabled.
  • Page 32 50 MB. • Before enabling BlackBerry user accounts, complete a baseline test of the system. To assess the impact of the BlackBerry user accounts on the Microsoft Exchange Server infrastructure, compare the baseline performance of the Microsoft Exchange Server to the performance of the Microsoft Exchange Server as you enable BlackBerry user accounts.

  • Page 33: Microsoft Sql Server 2000 Performance Test Results

    Performance impact considerations Overview of the test results This section provides information on the observed impact of the BlackBerry Enterprise Server on Microsoft SQL Server 2000. The performance tests measured the average processor time, average memory committed in bytes, average network bytes /sec, average disk transfers /sec, average SQL transactions /sec, and average user connection count.

  • Page 34: Processor Use

    17.22% when all 2000 BlackBerry user accounts were enabled. Out of all the features, RIM observed the largest increase in processor use when the BlackBerry MDS Connection Service along with the core BlackBerry features (email, calendar, and sent item redirection) were enabled.
  • Page 35 Two SCSI disks configured in a RAID 0+1 configuration were sufficient to handle the load placed on the remote Microsoft SQL Server disk subsystem from the BlackBerry Enterprise Server. See “Overview of the test results” on page 33 for more information.

  • Page 36: Transactions/Sec

    Microsoft SQL Server — percent disk time Transactions/sec The transaction /sec counter indicates the load that is placed on the Microsoft SQL Server by the BlackBerry Enterprise Server. During the performance testing, the maximum transaction rate was 18.79 /sec with all benchmarked features enabled for 2000 user accounts.

  • Page 37: User Connection Count

    Server establishes with the Microsoft SQL Server. The different BlackBerry components make their own connections to the database. In BlackBerry Enterprise Server Version 4.1.x, the number of connections for each BlackBerry component has been increased to avoid connection bottlenecks when you use Microsoft SQL Server 2000.

  • Page 38: Summary

    Microsoft SQL Server. The connection count and transaction rate are specific to the BlackBerry Enterprise Server that interacts with a remote Microsoft SQL Server. The BlackBerry Enterprise Server is designed to minimize the number of connections to the BlackBerry Configuration Database when MSDE is used instead of Microsoft SQL Server.

  • Page 39: Performance Impact Considerations

    If auto refresh is enabled, the BlackBerry Manager queries the BlackBerry Configuration Database at a rate that might result in a larger impact on the BlackBerry Configuration Database, depending on the rate set and the number of BlackBerry Managers that are open.
  • Page 40 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...

  • Page 41: Blackberry Enterprise Server Performance Test Results

    The following table shows the impact of BlackBerry user accounts on processor time and memory use when features are enabled. Test 1 was a baseline test (no BlackBerry user accounts) and has therefore been excluded. The counters in this table were collected using System Monitor on a Windows Server 2003.

  • Page 42: Processor Use

    22%. To determine the impact of each feature on the BlackBerry Enterprise Server, the Microsoft Exchange Server, and Microsoft SQL Server, each feature was run individually. The following chart illustrates that the processor time percentage was well within the recommended threshold of 75% for this counter.

  • Page 43: Memory Use

    BlackBerry Enterprise Server uses about 1.6 GB of memory. Because you can choose not to install the BlackBerry Collaboration Service and the BlackBerry MDS Services and because these components were not part of the benchmarking for this document, RIM did not install them. If these components are installed and running, even if they are not being used, a footprint is associated with them.

  • Page 44: Messages Queued For Delivery

    BlackBerry Enterprise Server either through notification or rescans that are waiting to be delivered to the BlackBerry device. The messages queued for delivery represent internal processing delays associated with processing this type of load when there are no wireless network delays and no users are outside of a wireless coverage area.

  • Page 45: Network Use

    4.22 Mbps with 2000 user accounts enabled. This is an increase in network traffic of approximately 0.95 Mbps. Overall, with all BlackBerry features enabled a link with 6 Mbps throughput would be required for a BlackBerry Enterprise Server for 2000 user accounts with this type of workload. The network traffic is a function of the...

  • Page 46: Performance Impact Considerations

    • Verify that the BlackBerry Enterprise Server hardware can handle increases in processor time use. Make sure that the BlackBerry Enterprise Server is not running at more than 75 % processor time on average, which is the maximum threshold. •...
  • Page 47 Collaboration Service and the BlackBerry MDS Services). Monitor total bytes each second on the BlackBerry Enterprise Server and make sure that enough bandwidth on the network is available to handle this traffic. The amount of data that is pushed or pulled through the BlackBerry MDS Connection Service also affects the bandwidth required.
  • Page 48 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...

  • Page 49: Conclusions

    Disk I/O activity increases when users on the messaging server are enabled for BlackBerry. To verify that enough disk space is present in the disk array, monitor the average disk queue length. For SAN disk implementations, measure sec/ transfer and make sure that this value is less than 20 ms.
  • Page 50 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking www.msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_5fs6.asp for more information about upgrading from MSDE 2000 to Microsoft SQL Server 2000.

  • Page 51: Appendix: Mmb And Mmb2 Comparison

    Overview Overview RIM measured the BlackBerry Enterprise Server performance using MAPI Messaging Benchmark 2 (MMB2), a standard developed by Compaq Computer Corporation (now Hewlett-Packard Development Company) and Microsoft to compare Microsoft Exchange Server performance with that of other servers. The MMB2 standard was adapted from MAPI Messaging Benchmark (MMB) to reflect the significantly higher peak load on the Microsoft Exchange Server 2000.
  • Page 52 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking Send messages (* messaging files created by the MMB2 workload) Properties MMB2 * file name: OupsXLatt.msg * file name: OupsBMobj.msg * file name: OupsXLobj.msg * file name:McPP1Matt.msg — * file name: McPP100katt.msg —...
  • Page 53 Appendix: MMB and MMB2 comparison Request meetings Properties MMB2 number of new meetings each day meeting length (in hours) minimum meeting length (in hours) average meeting length (in hours) maximum attendees minimum attendees average attendees maximum percentage of meeting requests with a distribution list Make appointment Properties MMB2...
  • Page 54 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking Create contacts Properties MMB2 number of times each day — Log on/log off Properties MMB2 log on at beginning of test log off at the end of each simulated day empty deleted items folder when logging off...

  • Page 55: Blackberry Attachment Service Traffic For Mmb2

    Seventeen percent of all messages contained attachments and each message was sent to an average of five recipients. With the current load test configuration, any message that contained an attachment was immediately requested for viewing on the BlackBerry device. During the load test scenarios, concurrent viewing of attachment requests occurred.
  • Page 56 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...

  • Page 57: Appendix: Blackberry Mds Connection Service Traffic Rate Derivation

    Fewer than two alerts occur each second. Because a maximum of four BlackBerry Messaging Agents are distributed for 2000 user accounts in the environment, the maximum number of alerts or push requests sent to the...
  • Page 58 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...

  • Page 59: Appendix: Calculations And Data

    = 25.24 accounts) with all benchmarked features enabled = 3.65 times y =%Processor Time, Test#1:baseline = 5.43 increase from the baseline value. z = increase in %Processor Time from enabling all BlackBerry user accounts for messaging and calendar Equation: increase ⎛...
  • Page 60 100% of BlackBerry user accounts (1000 user y =%Processor Time, Test#1:baseline = 5.43 accounts) for wireless message reconciliation = 3.29 times z = increase in %Processor Time from enabling all BlackBerry user accounts increase from the baseline value. for messaging and calendar Equation: increase ⎛...
  • Page 61 BlackBerry MDS Connection Service = MDS Connection Service enabled) = 4.22 0.95 Mbps y = (Network Mbps, Test#5: 2000 BlackBerry user accounts and BlackBerry MDS Connection Service turned off) = 3.27 z = increase in network use Equation: Therefore, the increase in network usage was 0.95 Mbps.
  • Page 62 BlackBerry Enterprise Server for Microsoft Exchange Performance Benchmarking...
  • Page 64 ©2006 Research In Motion Limited Published in Canada.

This manual is also suitable for:

Enterprise server 4.1

Table of Contents