Stress Test: lsalr

TEST NAME

lsalr - test network load bearing

SYNOPSIS

sh lsalr.sh remote_machine

DESCRIPTION

The lsalr test initiates several simultaneous directory-listing processes on a remote machine to test network load bearing.

This test initiates several remote ls -alR commands that run concurrently in the background.

OPERANDS

remote_machine

Either the host name or IP address of the machine to which files and directories are copied. If the host name is given, it must appear in /etc/hosts along with the remote machine's IP address.

USAGE VARIABLES

RUNTIME

Specifies, in seconds, the duration of the test. This variable is required only on the client side.

SETUP

You need two machines connected by a network, either back-to-back, or through a hub or switch.

OUTPUT

This test indicates its progress before and after each test iteration, and ends by displaying the total time the test ran.

DURATION

24 hours

POSSIBLE CONCURRENT TESTS

This test usually is run along with a second test to further stress the driver/NIC.

The runtime period should be set so that the test runs for as long as the concurrent tests are running. If this test is run independently, then 24 hours is sufficient.

This test can run concurrently with cl3se3, ftpstress, mpflip, and spray.

NOTES

This test might cause a problem if it runs too quickly, because it consumes all available sockets. After a socket is closed, the socket stays in the TIME_WAIT state for up to 2 minutes, during which it cannot be reused. For this reason, the test alters the tcp_time_wait_interval to a lower value as it runs.

EXAMPLES

# env RUNTIME=10 ./lsalr.sh moon
Running time: 10 seconds
!Pass:  No errors detected in lsalr.  Completed 6 iterations.

REFERENCES

ls(1), ssh(1), hosts(4)