Skip to content

Commit e7d8cc4

Browse files
committed
took out sizes for raw file tests
1 parent 2643227 commit e7d8cc4

File tree

2 files changed

+37
-17
lines changed

2 files changed

+37
-17
lines changed

README.md

Lines changed: 29 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -59,13 +59,12 @@ varied.
5959
-h Show this message
6060
-b binary name of fio binary, defaults to ./fio
6161
-d directory work directory where fio creates a file and reads and writes,
62-
default ./ (and default filename created is fiodata)
62+
default ./ (and default filename created is fiodata)
6363
-o directory results directory, where to put output files, defaults to ./
6464
-t tests tests to run, defaults to readrand,read,write
65-
options are
66-
readrand - IOPS test : 8k by 1,8,16,32 users
67-
read - MB/s t:w
68-
est : 1M by 1,8,16,32 users & 8k,32k,128k,1m by 1 user
65+
options are
66+
readrand - IOPS test : 8k by 1,8,16,32 users
67+
read - MB/s test : 1M by 1,8,16,32 users & 8k,32k,128k,1m by 1 user
6968
write - redo test, ie sync seq writes : 1k, 8k, 128k by 1 user
7069
randrw - workload test: 8k read and write by 1,8,16,32 users
7170
-s seconds seconds to run each test for, default 60
@@ -186,14 +185,19 @@ Start R and load up the above in R and it creates the dataframe "m"
186185

187186
In R we can now source "fio.r" which creates a function "graphit(m)"
188187

189-
source("fio.r")
190-
graphit(m)
188+
source("fio.r") # create the graphit() function
189+
source("data_ssd.r") # load some fio data, data_ssd.r is provided in github distro
190+
graphit(m) # graph the data
191+
source("fiog.r") # this will graph various combinations and save the png files
192+
# to C:\temp
193+
# the graphs will be for readrand, read and write tests
194+
# the graphs will graph different user loads and I/O sizes in the data
191195

192196
By default it will graph 8K random reads.
193197
If you source "fiog.r" it will run through a series of different combinations graphing them and saving the output.
194198
The output is save to png files in the directory C:\TMP
195199

196-
Three different example data files are included
200+
Example data files are included
197201

198202
* data_emc.r
199203
* data_ssd.r
@@ -203,7 +207,7 @@ Three different example data files are included
203207
collected from different systems. The EMC data is one single spindle. The pharos data is striped but
204208
shared filer. THe ssd data is from two striped SSD devices. The mem data is from using /tmp where /tmp
205209
is a memory filesystem.
206-
In order to tests these datasets, simple source them
210+
In order to graph these datasets, simple source them
207211

208212
source("data_ssd.r")
209213

@@ -222,7 +226,9 @@ you can set working directory with
222226

223227
for example to set it to C:\Temp
224228

225-
GRAPH Examples: https://sites.google.com/site/oraclemonitor/i-o-graphics#TOC-Percentile-Latency
229+
GRAPH Examples:
230+
231+
https://sites.google.com/site/oraclemonitor/i-o-graphics#TOC-Percentile-Latency
226232

227233

228234
Running fiop.r and fiopg.r
@@ -234,21 +240,25 @@ for example
234240
source("data_emc.r")
235241
source("fiopg.r")
236242

237-
There three graphs
243+
Each PNG file will have 3 graphs
244+
238245
1. latency on a log scale
239246
2. latency on a base 10 scale
240247
3. throughout MB/s
241248

242249
1: the log scale latency has several parts
243250
-------------------------------------------
244-
+ 4 lines
251+
252+
Four lines:
245253

246254
1. max latency - dashed red line
247255
2. 99% latency - top of light grey shaded area
248256
3. 95% latency - top of dark grey shaded area
249257
4. avg latency - black line
250258

251-
+ back ground is shaded with bars 0 percent at bottom to 100% at top
259+
Plus:
260+
261+
+ back ground is barchaerts, 0 percent at bottom to 100% at top
252262

253263
light blue % of I/Os below 1ms - probably some sort of cache read
254264
green % of I/Os below 10ms
@@ -276,18 +286,23 @@ There three graphs
276286
the bars are color code with amount percentage of throughput that had a latency of that color where colors
277287
are in the right hand axis legend in top graph the latency on log scale
278288

279-
see: https://sites.google.com/site/oraclemonitor/i-o-graphics#TOC-percentile-latency-with-scaling
289+
see:
290+
291+
https://sites.google.com/site/oraclemonitor/i-o-graphics#TOC-percentile-latency-with-scaling
280292

281293

282294
New Graphics
283295
-----------------------------------------------------
284296
a new version of the function graphit() is created by
285297
fiop.r and fiopg.r will go through a set of I/O data
286298
and print out variouis graphs of the data.
299+
287300
Examples of the graphs are on
301+
288302
https://plus.google.com/photos/105986002174480058008/albums/5773655476406055489?authkey=CIvKiJnA2eXSbQ
289303

290304
A visual explanation is here
305+
291306
https://plus.google.com/photos/105986002174480058008/albums/5773661884246310993
292307

293308
A Summary of the graph contents is:

fio.sh

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -278,9 +278,14 @@ if [ x$FILENAME == x ] ; then
278278
fi
279279
OFFSET=0
280280
fi
281-
if [ $RAW -eq 1 ] ; then
282-
SIZE="size=${MEGABYTES}m"
283-
fi
281+
#
282+
# Looks like RAW will determine the
283+
# device size and not use the size
284+
# given in the input
285+
#
286+
#if [ $RAW -eq 1 ] ; then
287+
# SIZE="size=${MEGABYTES}m"
288+
#fi
284289

285290

286291
mkdir $OUTPUT > /dev/null 2>&1

0 commit comments

Comments
 (0)