TEST - OMS Administration Utility Command
Description
The TEST command executes a disk write test to provide a simple measure of a file system performance. The write test is performed in a manner that simulates the I/O methods used by the OMS Server when writing OMS messages to the OMS message database.
I/O performance of a file system is dependent on many factors. A detailed analysis of the performance of an I/O subsystem is beyond the scope of this document. The purposes of the test I/O command is to provide general performance numbers to evaluate the suitability of the file system for the OMS server message database.
The test I/O command writes a specified number of 512-byte blocks to a specified file. By default, each block is flushed to disk to simulate the I/O pattern of the OMS server. The flush interval can be specified to match the configured flush interval of the OMS server.
Some general guidelines for performing an I/O test:
- I/O subsystem performance will vary considerably due to a number of factors, so the test should be performed a number of times to get a good statistical sampling.
- The I/O test file must reside on the file system being considered for the OMS message database.
- The OMS Administration Utility command must be executed from the system on which the OMS server executes. If the file system being tested is a network based file system, this is particular important in order to know the network performance impact as well.
The I/O test will print the results of the test as the number of blocks written per second. As a general guideline, the following table categorizes the message rate.
Rate | Category |
---|---|
> 500 | fast |
300 - 499 | medium |
100 - 299 | slow |
< 100 | very slow |
Command Line Syntax
The following figure illustrates the command line syntax of the TEST command, using the command line, long form of its command options.
-test io -iocount iocnt -iofile iofile [-ioflush ioflushcnt] [-codepage codepage] [-file cmfile] [-encryptedfile ecmfile [-key ecmdkey]] [-level msglevel] [-nls_directory directory] [-port port]
Command Options
The following table describes all TEST command options and provides the command line, long form of each option illustrated in the TEST command line syntax, above.
Command | Command Line | Description |
---|---|---|
-iocnt | Number of 512-byte blocks to write in the I/O write test. | |
-iofile | File name used for the I/O write test. | |
-ioflushcnt | Frequency in which data is flushed to disk as part of the I/O write test. | |
-codepage | Local code page used to translate text data from and to the OMS Server. | |
-file | Command file that contains OMS Administration Utility (omsadm) command line options. | |
-encryptedfile | Command file encrypted by the Universal Encrypt (uencrypt) utility. | |
-key | Encryption key used to encrypt the encrypted command file. | |
-level | Severity level of messages to be written. | |
-nls_directory | Directory in which to find the Universal Translation Table (UTT) file specified by the CODE_PAGE command option. | |
-port | TCP port on which the OMS Server is listening for connections. |
Examples
The following example executes an I/O test in the default OMS message database directory on UNIX systems. The example writes 1000 512-byte blocks to the test file iotest
.
The user must have sufficient permissions to the OMS message database directory to create the iotest
file.
omsadm -test io -iofile /var/opt/universal/spool/oms/iotest -iocount 1000
The output of the above command will provide the number of 512-byte blocks written per second.
UNV6105I I/O write test: count=1000, flush interval=1, rate=761.61 blocks/sec.