From: Joseph Gmitter Date: Wed, 7 Dec 2016 16:19:50 +0000 (-0500) Subject: LUDOC-292 fix: Update formatting error in file path X-Git-Tag: 2.9.0~4 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=13f5fa1a8864818c97a8db205d80351d3ce38e3f;p=doc%2Fmanual.git LUDOC-292 fix: Update formatting error in file path At some point the following line was changed in the Visualizing Results section of the benchmarking section of the manual: /proc/fs/lustre/obdfilter/*/brw_stats was accidentally changed to: /proc/fs/lustre/obdfilter/ Also, "*/brw_stats" appeared in a tag, which was not the intent. The patch also updates these 3 paragraph for 80 character max per line. Signed-off-by: Joseph Gmitter Change-Id: I10f2a40cd06ee2403c8cb1545302e4c3da03a3b2 Reviewed-on: https://review.whamcloud.com/24200 Tested-by: Jenkins --- diff --git a/BenchmarkingTests.xml b/BenchmarkingTests.xml index 953659b..7369fdf 100644 --- a/BenchmarkingTests.xml +++ b/BenchmarkingTests.xml @@ -612,14 +612,22 @@ over all OSTs.
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 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. + 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/*/brw_stats + (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. + 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.