This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Performance benchmarks for Data Management

BMC measured performance benchmarks for the uses of the ITSM 8.1 dataload tool and data wizard, which are described in this topic:

Note

Performance is specific to your environment. The performance information provided below reflects typical uses of the Data Management features. You will still need to test the performance in your environment.

Performance benchmarks for loading data

This section shows the length of time to load specified data using the Data Management dataload tool in the BMC Software performance lab.

Records information

Testing was performed using the following number of records:

Total number of records

% Foundation

% Transactional

% Process Setup

110,000

11% (10,000 people records)

89% (100,000 incident records)

0%

Incident load

This section shows how many records per hour were processed by the dataload tool in the BMC Software performance lab for the import of 100,000 incident records.

The following incident load was run with an Assigned status. No work logs or tasks were attached to the incidents.

The incident load was run with 3 server threads.  For more information on configuring for multi-threading, see Configuring performance enhancements for Data Management.

The Replace Case/Alias field for the job was set to No and the Create Only flag was left unchecked.

Tasks

Throughput

Load, Validate, Promote

54,895 incident records per hour

People load

This section shows how many records per hour were processed by the dataload tool in the BMC Software performance lab for the import of 10,000 people records.

The people load was run with 3 server threads.

The Replace Case/Alias field for the job was set to No and the Create Only flag was left unchecked.

Tasks

Throughput

Load, Validate, Promote

24,674 people records per hour

Hardware/software environment

The performance benchmarks were performed in the following environment:

Operating system

Tier

CPU

Processor

Memory

VM

Network

Microsoft Windows Server 2008 x64

BMC Remedy AR System

2 x 2.4 GHz

2.66 Ghz Intel Xenon

4 GB

Yes

1 Gbps

Microsoft Windows Server 2008 x64

BMC Remedy Mid Tier

2 x 2.4 GHz

2.66 Ghz Intel Xenon

4 GB

Yes

1 Gbps

Red Hat Enterprise Linux

Reverse Proxy

1 CPU

N/A

2 GB

Yes

1 Gbps

Windows Server 2008 x64

SQL 2008 x64

2 x 2.4 GHz Quad Core

N/A

24 GB

No

1 Gbps

The database server has multiple SQL server instances.

The BMC Remedy AR System server was configured for multi-threading, as described in Configuring performance enhancements for Data Management.

Performance benchmarks for modifying records with the data wizard

This section shows the length of time to process specified data using the data wizard tool in the BMC Software performance lab.

Performance benchmarks for updating company fields on the Incident form (HPD:Help Desk form)

Total number of records

Number of affected records

Time to complete updates

500,000

250,000

41 seconds

500,000

0

17.6 seconds

1,000,000

500,000

2 minutes, 27 seconds

1,000,000

250,000

1 minute, 31 seconds

1,000,000

0

1 minute, 10 seconds

Hardware environment

The performance benchmarks were performed on one Dell PowerEdge 2950 server connected to a LAN. The server has one 1.86 GHz Intel E5320 processor (4 cores), 8 GB RAM, and two local hard drives.

Software environment

The following table indicates the software environment for the two servers.

Software environment for performance benchmark lab during data wizard testing

Component

Version

Running on

Windows 2003 server

Enterprise Edition SP2

Dell PowerEdge 2950

BMC Remedy AR System server

7.0.1 patch 006

Windows 2003 Server

BMC Remedy ITSM applications

7.0.3 patch 006

Windows 2003 Server

Oracle 10g R2

10.2.0.1

Windows 2003 Server

For Oracle configuration, the initialization parameters were set as follows:

  • sga_target=1224M
  • pga_aggregate_target=800M

Data files were on one hard drive, while all the online redo log files were on another dedicated hard drive.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments