[Trivial Fix] Correct spelling error of "bandwidth"
Small modification to correct spelling mistake. Change-Id: I7b88f1385159934729d3c305bf3c47b7f8498520
This commit is contained in:
parent
b892985a56
commit
984d6bde22
@ -157,7 +157,7 @@ RUNMOD="${RUNMOD}"
|
||||
PARSEONLY="${PARSEONLY:-false}"
|
||||
|
||||
# Output format:
|
||||
# starttime, endtime, Jobname, read IOPS, read bandwith KB/s, mean read complete latency msec, avg read latency msec, avg read bandwith KB/s, write IOPS, write bandwith KB/s, mean write complete latency msec, avg write latency msec, avg write bandwith KB/s
|
||||
# starttime, endtime, Jobname, read IOPS, read bandwidth KB/s, mean read complete latency msec, avg read latency msec, avg read bandwidth KB/s, write IOPS, write bandwidth KB/s, mean write complete latency msec, avg write latency msec, avg write bandwidth KB/s
|
||||
if [[ "${PARSEONLY}" == "true" ]]; then
|
||||
for tline in $(cat "${1}")
|
||||
do
|
||||
|
@ -301,8 +301,8 @@ concurrent loads.
|
||||
|
||||
- As a result of this part we got the following CSV files in following format
|
||||
starttime,stoptime,jobname,
|
||||
read_iops,read_bandwith,read_complelatency_mean,read_complelatency_min,read_complelatency_max,read_complelatency_95%ile,read_complelatency_99%ile,read_total_latency_avg,read_bandwith_avg,
|
||||
write_iops,write_bandwith,write_complelatency_mean,write_complelatency_min,write_complelatency_max,write_complelatency_95%ile,write_complelatency_99%ile,write_total_latency_avg,write_bandwith_avg.
|
||||
read_iops,read_bandwidth,read_complelatency_mean,read_complelatency_min,read_complelatency_max,read_complelatency_95%ile,read_complelatency_99%ile,read_total_latency_avg,read_bandwidth_avg,
|
||||
write_iops,write_bandwidth,write_complelatency_mean,write_complelatency_min,write_complelatency_max,write_complelatency_95%ile,write_complelatency_99%ile,write_total_latency_avg,write_bandwidth_avg.
|
||||
|
||||
:download:`METRICS(NUMBER_OF_VM_WORKERS=2) <results/cinder_ceph/02/2.csv>`
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user