Flexible I/O Tester development
 help / color / mirror / Atom feed
* Different percentages of job activity on a single drive, along with different i/o sizes for each drive
@ 2014-08-08  7:49 Nicholas Krone
  0 siblings, 0 replies; only message in thread
From: Nicholas Krone @ 2014-08-08  7:49 UTC (permalink / raw)
  To: fio

Hi,

I'm currently trying to use FIO for some drive endurance testing and I 
have a few questions that I was hoping you guys could answer.

I need to stress a drive with a split blocksize range and ensure write 
verifications. Here's a small job I drafted up:

For example, a 100GB drive to test

[global]
ioengine=noop
ioengine=libaio
iodepth=4
rw=randwrite
direct=1
bssplit=512b/4:1024b/1:1536b/1:2048b/1:2560b/1:3072b/1:3584b/1:4096b/67:8192b/10:16384b/7:32768b/3:65536b/3 

do_verify=1
verify=meta
verify_backlog=512
error_dump=1
verify_dump=1
verify_fatal=1

[50-pct-ratio]
offset=0
size=5%

[30-pct-ratio]
offset=6g
size=15%

[20-pct-ratio]
offset=21g
size=80%


0-5% - 50 PCT write access (5 GB I/O size)
6%-20% - 30 PCT write access (15 GB I/O size)
21%-100% - 20 PCT write acces (80 GB I/O size)

Will using 3 sets of size params in each job work out correctly? Also, 
If during one of the jobs, a write verification occurs, will all the 
jobs fully stop because it wouldn't make sense for any of the test to 
continue if any write errors occur.

I read about the flow counter and a way control activity between jobs 
but I'm really unclear as to how implement it and the example didn't 
really help me out.

[50-pct-ratio]
flow=-2

[30-pct-ratio]
flow=3

[20-pct-ratio]
flow=5

Am I on the right track on anything? Any help would be great.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2014-08-08  7:49 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-08  7:49 Different percentages of job activity on a single drive, along with different i/o sizes for each drive Nicholas Krone

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox