HP StorageWorks Scalable File Share - Manual (Page 167)

Verifying the system 6–37
When you have ensured that no other processes are accessing the file system, enter the
ost_perf_check.bash
command on the client node, using the following syntax:
/usr/opt/hpls/diags/bin/ost_perf_check.bash --serial --mount-point mount_point
--remote-shell remote_shell
where
mount_point
is the directory where the file system is mounted on the client node.
The command tests the speed at which the single client node can read from and write to each OST service
in the file system in turn, by creating a file of a single stripe on a single OST service and using the
IOR
utility
to read and write data to the file.
When the test finishes, the speeds at which the client could read from and write to each particular OST
service are displayed, as shown in this example:
# ./ost_perf_check.bash --serial --mount-point /mnt/lustre --remote-shell ssh
== Testing write on OST 0 ==
Maximum wall clock deviation: 0.00 sec
Max Write: 72.97 MiB/sec (76.51 MB/sec)
== Testing write on OST 1 ==
Maximum wall clock deviation: 0.00 sec
Max Write: 72.31 MiB/sec (75.83 MB/sec)
== Testing read on OST 0 ==
Maximum wall clock deviation: 0.00 sec
Max Read: 135.87 MiB/sec (142.47 MB/sec)
== Testing read on OST 1 ==
Maximum wall clock deviation: 0.00 sec
Max Read: 123.95 MiB/sec (129.97 MB/sec)
Compare the results of these tests with the expected performance details provided in Appendix B. Note that
the maximum performance observed will be the lower of the two values of the maximum performance for
either the interconnect type or the maximum performance for the storage type.
6.1.9.2 Parallel OST service tests
To run the parallel tests, both the client node where you run the test and the last client node in the list passed
to the command must be able to connect to all of the other client nodes that are to be used in testing, using
either the
ssh
utility without a password or the
rsh
utility without a password. If you are using the
rsh
utility, you must add
--remote_shell rsh
to the command line.
If the sequential test shows that each OST service is running at an appropriate speed, run parallel tests to
make sure that the performance of the network and the OST services is scaling appropriately.
To check the performance fully, one client node is required for each OST service in the HP SFS system. Before
you run the parallel OST service test, run the sequential test described in Section 6.1.9.1 on each client node
that you intend to use in the parallel test.
Note that if for any reason you are using an odd number of client nodes, the results of the parallel tests may
not be reliable for read operations, as it is possible that one of the clients may be reading from cache. To
avoid this situation, ensure that you only run this test with even numbers of Object Storage Servers and client
nodes.
Before you run the parallel test, make sure that the file system is correctly mounted on all of the client nodes
that you intend to use for the test. To ensure that the test is reliable, unmount the file system from all client
nodes that are not involved in the test so that they are not able to use the file system in any way.
When you have ensured that no other processes are accessing the file system, enter the
ost_perf_check.bash
command on one of the client nodes, using the following syntax:
/usr/opt/hpls/diags/bin/ost_perf_check.bash --parallel --mount-point mount_point
--remote-shell remote_shell --clients "client_name1 [client_name2 ...]"
where
mount_point
is the directory where the file system is mounted on each of the client nodes (the
mount point must be the same for all client nodes). The client list in the command must contain as many client
nodes as there are OST services in the file system to be tested.