IOPS for CommServe Database Volumes

Table of Contents

Overview

This document describes how to plan for and measure Input Output Operations per second (IOPS) when commissioning disk storage to store the CommServe database.

The CommServe database volume stores the Microsoft SQL database that acts as a central repository for CommCell-wide configuration information. Since nearly every operation depends on this central critical resource, it is recommended that this volume be on a fast disk for overall performance.

The following section explains the use of IOmeter which is an open source industry standard tool for measuring IOPS. Using IOPS rating provides a standard and simplified way to commission storage without having to understand and use proprietary tools.

CommServe Database Recommendation

The CommServe database must be hosted on a separate volume that meets the IOPS requirement described in the CommServe - Hardware Specifications.

Running IOmeter

Worker thread is an entity that runs the test defined under the Access Specification Tab of the IOmeter User Interface. Multiple worker threads run the tests in parallel to test concurrent performance.

Before You Begin

We recommend that you run IOmeter on the physical disk that represents the storage volume for which IOPS need to be measured. IOmeter allows physical disks to be selected only when there are no volumes on the disk.

Procedure

  1. Go to the software_installation_directory/Base folder, right-click IOmeter, and then click Run as Administrator.
  2. In the license dialog box, click I Agree.

  3. In the Topology pane, expand All Manager > computer_name, delete all worker threads except one by selecting the worker thread and clicking the Disconnect Selected Worker or Manager icon.
  4. On the Disk Targets tab, select the appropriate options:
    1. Select a disk to use in the test ().
      • represents physical drives that have no partitions on them.
      • represents drives that need to be prepared before the test. These are the volumes that do not contain the iobw.tst file.

        Before running a test on a volume, IOmeter must prepare the volume. It creates a file named iobw.tst as part of this preparation phase and runs read/write tests on this file.

      • represents the logical (mounted) drives that are prepared and contain the iobw.tst file.
    2. In the Maximum Disk Size and Starting Disk Sector boxes, set the default value to 0.
  5. On the Access Specifications tab, in the Global Access Specifications box, create the IOmeter profile for testing the CommServe database volume:
    1. Double-click Default.
    2. In the Edit Access Specification dialog box, change the following:
      • The Transfer Request Size to 64K Block Size
      • The Percent of Access Specification to 100%
      • The Percent Read/Write Distribution to 67% reads and 33% writes
      • The Percent Random/Sequential Distribution to 100% random
    3. Click Add.

    This profile closely emulates the way a disk is accessed by MS SQL database lookups.

  6. To run IOPS with multiple worker threads, from the IOmeter toolbar, click Start a Duplicate of This Worker on This Manager to create a duplicate worker thread with the same settings.

    Repeat this step to create a total of 8 worker threads.

  7. On the Results Display tab, set the Update Frequency to 5 seconds.
  8. On the Test Setup tab, under Run Time, in the Minutes box, enter 30.
  9. From the IOmeter toolbar, click Start Tests to start the test.
  10. In the Save Results dialog box, select a file to store the test results, and click Save.

    After a few seconds the test result appears on the Results Display tab.

  11. Run the test for approximately 30 minutes or until the IOPS value has stabilized.
  12. Click Stop Current Test and Save Results .

    The test stops and the final results are saved in the results.csv file.

  13. Record the IOPS test rating.
  14. If you are running IOmeter on a volume, delete iobw.tst file after the test is complete.
  15. Recreate the volume on the disk with the same drive letter or mount path.

    If required format the volume.

  16. Copy all the data from the temporary folder back to the volume.
  17. Start all services.

    For instructions, see Starting a Service.