From: Richard Henwood Date: Fri, 20 May 2011 18:17:07 +0000 (-0500) Subject: FIX: validation, ulink -> link X-Git-Tag: proofedversion~9 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=b415cb6368bbe9bfc8cbb366928fe2b2b77f9fe1;p=doc%2Fmanual.git FIX: validation, ulink -> link --- diff --git a/BenchmarkingTests.xml b/BenchmarkingTests.xml index 4a391ea..6d930fb 100644 --- a/BenchmarkingTests.xml +++ b/BenchmarkingTests.xml @@ -178,18 +178,18 @@ MB/s Run the script using the case=disk parameter to run the test against all the local OSTs. The script automatically detects all local OSTs and includes them in the survey. To run the test against only specific OSTs, run the script using the target=parameter to list the OSTs to be tested explicitly. If some OSTs are on remote nodes, specify their hostnames in addition to the OST name (for example, oss2:lustre-OST0004). All obdfilter instances are driven directly. The script automatically loads the obdecho module (if required) and creates one instance of echo_client for each obdfilter instance in order to generate I/O requests directly to the OST. - For more details, see Testing Local Disk Performance. + For more details, see . Network - In this mode, the Lustre client generates I/O requests over the network but these requests are not sent to the OST file system. The OSS node runs the obdecho server to receive the requests but discards them before they are sent to the disk. - Pass the parameters case=network and target=<hostname|IP_of_server> to the script. For each network case, the script does the required setup. - For more details, see Testing Network Performance + Pass the parameters case=network and target=<hostname|IP_of_server> to the script. For each network case, the script does the required setup. + For more details, see Remote file system over the network - In this mode the obdfilter_survey script generates I/O from a Lustre client to a remote OSS to write the data to the file system. + To run the test against all the local OSCs, pass the parameter case=netdisk to the script. Alternately you can pass the target= parameter with one or more OSC devices (e.g., lustre-OST0000-osc-ffff88007754bc00) against which the tests are to be run. + For more details, see . - To run the test against all the local OSCs, pass the parameter case=netdisk to the script. Alternately you can pass the target= parameter with one or more OSC devices (e.g., lustre-OST0000-osc-ffff88007754bc00) against which the tests are to be run. - For more details, see Testing Remote Disk Performance. The obdfilter_survey script is destructive and should not be run on devices that containing existing data that needs to be preserved. Thus, tests using obdfilter_survey should be run before the Lustre file system is placed in production. @@ -233,7 +233,7 @@ MB/s Verify that the obdecho module is loaded. Run: - modprobe obdecho + modprobe obdecho Determine the OST names. @@ -276,7 +276,7 @@ lustre-OST0002' sh obdfilter-survey lctl dl - Run the obdfilter_survey script with the parameters case=network and targets=<hostname|ip_of_server>. For example: + Run the obdfilter_survey script with the parameters case=network and targets=<hostname|ip_of_server>. For example: $ nobjhi=2 thrhi=2 size=1024 targets='oss1 oss2' case=network sh obdfilte\ sh odbfilter-survey @@ -331,10 +331,10 @@ sh odbfilter-survey List all OSCs you want to test. - Use the target=parameter to list the OSCs separated by spaces. List the individual OSCs by name seperated by spaces using the format <fsname>-<OST_name>-osc-<OSC_number> (for example, lustre-OST0000-osc-ffff88007754bc00). You do not have to specify an MDS or LOV. + Use the target=parameter to list the OSCs separated by spaces. List the individual OSCs by name seperated by spaces using the format <fsname>-<OST_name>-osc-<OSC_number> (for example, lustre-OST0000-osc-ffff88007754bc00). You do not have to specify an MDS or LOV. - Run the obdfilter_survey script with the target=parameter and case=netdisk. + Run the obdfilter_survey script with the target=parameter and case=netdisk. An example of a local test run with up to two objects (nobjhi), up to two threads (thrhi), and 1024 Mb (size) transfer size is shown below: $ nobjhi=2 thrhi=2 size=1024 \ targets="lustre-OST0000-osc-ffff88007754bc00 \ @@ -496,7 +496,7 @@ sh odbfilter-survey
24.3.4.2 Visualizing Results It is useful to import the obdfilter_survey script summary data (it is fixed width) into Excel (or any graphing package) and graph the bandwidth versus the number of threads for varying numbers of concurrent regions. This shows how the OSS performs for a given number of concurrently-accessed objects (files) with varying numbers of I/Os in flight. - It is also useful to monitor and record average disk I/O sizes during each test using the 'disk io size' histogram in the file /proc/fs/lustre/obdfilter/ (see Watching the OST Block I/O Stream for details). These numbers help identify problems in the system when full-sized I/Os are not submitted to the underlying disk. This may be caused by problems in the device driver or Linux block layer. + It is also useful to monitor and record average disk I/O sizes during each test using the 'disk io size' histogram in the file /proc/fs/lustre/obdfilter/ (see for details). These numbers help identify problems in the system when full-sized I/Os are not submitted to the underlying disk. This may be caused by problems in the device driver or Linux block layer. */brw_stats The plot-obdfilter script included in the I/O toolkit is an example of processing output files to a .csv format and plotting a graph using gnuplot.
@@ -604,7 +604,7 @@ Ost index 2 Read time 0.14 Write time \ sh gather_stats_everywhere.sh config.sh stop <log_name.tgz> When <log_name.tgz> - is specified, a profile tarball /tmp/<log_name.tgz> is created. + is specified, a profile tarball /tmp/<log_name.tgz> is created. Analyze the collected statistics and create a csv tarball for the specified profiling data.