X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=lustre-iokit%2Fsgpdd-survey%2FREADME.sgpdd-survey;h=7d793bf8f97546f6da6c71413df13b090769fc66;hb=f6d744d259fe6bc0b8750127565fb13fb2e66c06;hp=c1f3337bbd09e31bdfafd32084ae3020ece2ec5d;hpb=b4509fffd850e86442c49d5c03b341c75a492a76;p=fs%2Flustre-release.git diff --git a/lustre-iokit/sgpdd-survey/README.sgpdd-survey b/lustre-iokit/sgpdd-survey/README.sgpdd-survey index c1f3337..7d793bf 100644 --- a/lustre-iokit/sgpdd-survey/README.sgpdd-survey +++ b/lustre-iokit/sgpdd-survey/README.sgpdd-survey @@ -58,11 +58,12 @@ ${rslt}_.detail collected tmp files for post-mortem The summary file and stdout contain lines like... -total_size 8388608K rsz 1024 thr 1 crg 1 180.45 MB/s 1 x 180.50 = 180.50 MB/s +dev 30 sz 125829120K rsz 1024K crg 60 thr 120 write 6036.79 [ 100.69, 106.49] read 6720.94 [ 112.64, 220.85] -The number immediately before the first MB/s is the bandwidth computed by -measuring total data and elapsed time. The other numbers are a check on -the bandwidths reported by the individual sgp_dd instances. +The number immediately after the write and the read word is the bandwidth +in MiB/s computed by measuring total data and elapsed time. The other numbers +are the minimal and maximal bandwidths reported by the individual sgp_dd +instances. If there are so many threads that sgp_dd is unlikely to be able to allocate I/O buffers, "ENOMEM" is printed. @@ -80,7 +81,7 @@ with varying queue depth. If the series (varying numbers of concurrent regions) all seem to land on top of each other, it shows the device is phased by seeks at the given record size. -The included script "plot-sgpdd" will process output files and create -.dat (similar to csv) files for spreadsheet import. It also plots the -results directly using gnuplot and creates .png files. +The included script "iokit-plot-sgpdd" will process output files and +create .dat (similar to csv) files for spreadsheet import. It also plots +the results directly using gnuplot and creates .png files.