Each test employed a single client writing (and reading) a single file to an increasing number of OST's. This is a file-per-process test. In this phase the OST's are assigned such that a two stripe file will utilize two OST's each on a separate OSS node. A four stripe file will utilize 4 OST's on four OSS's. (Note: this differs from phase 1 testing due to file-system reconfiguration) Stripe size is limited by lustre to be the minimum of either the number of OST's configured in the file-system or 160 (in this test the number of OST's used were limited to 56 to more meaningfully compare with phase 1 results).
One purpose of this test is to measure the ability of the client to source or put data. By providing a sink that should exceed the network bandwidth we should be able to determine if the client is a performance bottle-neck.
AVG PER OST Performance
Y- MiB/sec aggregate transfer for each datapoint
X - <clients.stripe> constant client count of 1, increasing stripe count from 2-56.
TEST CODE: IOR
MAX OST's: 56
MAX OSS's: 28
Phase 1 - TEST1
Data in TABLE format