Lines Matching refs:job
33 writing a job file describing that specific setup. A job file may contain
34 any number of threads and/or files - the typical contents of the job file
35 is a global section defining shared parameters, and one or more job
37 and sets everything up as described. If we break down a job from top to
68 job behaves.
76 Running fio is normally the easiest part - you just give it the job file
77 (or job files) as parameters:
82 more than one job file on the command line, fio will serialize the running
86 If the job file contains only one job, you may as well just give the
88 to the job parameters, with a few extra that control global parameters
89 (see README). For example, for the job file parameter iodepth=2, the
91 also use the command line for giving more than one job entry. For each
92 --name option that fio sees, it will start a new job with that name.
93 Command line entries following a --name entry will apply to that job,
95 similar to the job file options, where each option applies to the current
96 job until a new [] job entry is seen.
99 in the job section requires that. Some other options may also be restricted,
105 As previously described, fio accepts one or more job files describing
106 what it is supposed to do. The job file format is the classic ini file,
107 where the names enclosed in [] brackets define the job name. You are free
109 A global section sets defaults for the jobs described in that file. A job
110 may override a global section parameter, and a job file may even have
111 several global sections if so desired. A job is only affected by a global
115 So let's look at a really simple job file that defines two processes, each
118 ; -- start job file --
127 ; -- end job file --
129 As you can see, the job file sections themselves are empty as all the
132 line, this job would look as follows:
140 ; -- start job file --
150 ; -- end job file --
152 Here we have no global section, as we only have one job defined anyway.
156 to their own 64MB file. Instead of using the above job file, you could
163 desirable to share a set of standardized settings across multiple job files.
167 ; -- start job file including.fio --
179 ; -- end job file including.fio --
181 ; -- start job file glob-include.fio --
184 ; -- end job file glob-include.fio --
186 ; -- start job file test-include.fio --
189 ; -- end job file test-include.fio --
200 fio also supports environment variable expansion in job files. Any
207 As an example, let's look at a sample fio invocation and job file:
211 ; -- start job file --
216 ; -- end job file --
218 This will expand to the following equivalent job file at runtime:
220 ; -- start job file --
225 ; -- end job file --
227 fio ships with a few example job files, you can also look there for
240 These can be used on the command line or in the job file, and will be
241 automatically substituted with the current system values when the job
254 This section describes in details each parameter associated with a job.
299 With the above in mind, here follows the complete list of fio job
302 name=str ASCII name of the job. This may be used to override the
303 name printed by fio for this job. Otherwise the job
306 job.
308 description=str Text description of the job. Doesn't do anything except
309 dump this text description when this job is run. It's
316 filename=str Fio normally makes up a filename based on the job name,
318 files between threads in a job or several jobs, specify
324 ':' colon. So if you wanted a job to open /dev/sda and /dev/sdb
360 file number 4 for any job will be named testfiles.4. The
463 size=int The total size of file io for this job. Fio will run until
468 between the available files specified by the job. If not set,
631 nrfiles=int Number of files to use for this job. Defaults to 1.
637 file_service_type=str Defines how fio decides which file from a job to
654 ioengine=str Defines how the job issues io to the file. The following
712 will cause that job to do nothing but burn
766 job file to create such files, use rw=write
778 job, can be overridden with a larger value for higher
829 each sub-job (i.e. when numjobs option is specified). This
841 condition is met before other end-of-job criteria.
879 file close, not just at the end of the job.
950 nice=int Run the job with the given nice value. See man nice(2).
952 prio=int Set the io priority value of this job. Linux limits us to
958 thinktime=int Stall the job x microseconds after an io has completed before
979 rate=int Cap the bandwidth used by this job. The number is in bytes/sec,
990 the job to exit. The same format as rate is used for
995 job is given a block size range instead of a fixed value,
1000 the job to exit. The same format as rate is used for read vs
1009 that the job is run at varying queue depths to test the
1017 max_latency=int If set, fio will exit the job if it exceeds this maximum
1023 cpumask=int Set the CPU affinity of this job. The parameter given is a
1024 bitmask of allowed CPU's the job may run on. So if you want
1044 split Each job will get a unique CPU from the CPU set.
1048 one cpu per job. If not enough CPUs are given for the jobs
1051 numa_cpu_nodes=str Set this job running on spcified NUMA nodes' CPUs. The
1056 numa_mem_policy=str Set this job's memory policy and corresponding NUMA
1067 startdelay=time Start this job the specified number of seconds after fio
1068 has started. Only useful if the job file contains several
1074 a specified job will run, so this parameter is handy to
1086 that the ramp_time is considered lead in time for a job,
1117 bs size for the job, multiplied by the io depth given. Note
1123 job file, add up the io depth of all jobs (normally one unless
1150 exitall When one job finishes, terminate the rest. The default is
1151 to wait for each job to finish, sometimes that is not the
1171 create_only=bool If true, fio will only run the setup phase of the job.
1173 that will be done. The actual job contents are not
1184 unlink=bool Unlink the job files when done. Not the default, as repeated
1185 runs of that job would then waste time recreating the file
1188 loops=int Run the specified number of iterations of this job. Used
1203 after each iteration of the job. The allowed values are:
1286 option is set, fio will exit the job on the first observed
1308 job that utilizes verify once that job has completed. In
1325 verify_state_save=bool When a job exits during the write phase of a verify
1338 pass, according to the settings in the job file used.
1341 wait_for_previous Wait for preceding jobs in the job file to exit, before
1343 points in the job file. A stone wall also implies starting
1348 numjobs=int Create the specified number of clones of this job. May be
1355 groups of jobs as a whole instead of for each individual job.
1358 To see the final report per-group instead of per-job, use
1374 read_iolog. Specify a separate file for each job, otherwise
1411 write_bw_log=str If given, write a bandwidth log of the jobs in this job
1417 x is the index of the job (1..N, where N is the number of
1429 and foo_lat.x.log, where x is the index of the job (1..N,
1435 "jobname_type.x.log" is used,where x is the index of the job
1474 exec_prerun=str Before running this job, issue the command specified
1478 exec_postrun=str After the job completes, issue the command specified
1551 continue_on_error=str Normally fio will exit the job on the first observed
1552 failure. If this option is set, fio will continue the job when
1591 cgroup=str Add job to this control group. If it doesn't exist, it will
1603 the job completion. To override this behavior and to leave
1604 cgroups around after the job completion, set cgroup_nodelete=1.
1606 files after job completion. Default: false
1622 one job has flow=8 and another job has flow=-1, then there
1626 counter is allowed to reach before the job must wait for a
1653 If the job is a TCP listener or UDP reader, the hostname is not
1659 with numjobs to spawn multiple instances of the same job type, then this will
1685 as well as the hostname if the job is a TCP listener or UDP
1765 first character is the first job defined in the job file, and so forth.
1814 IO depths= The distribution of io depths over the job life time. The
1865 running, without terminating the job. To do that, send fio the USR1 signal.
1879 A description of this job goes here.
1881 The job description (if provided) follows on a second line.
2007 first is a normal write job of some sort with verify enabled. When the
2010 on running the same job (but with reads instead of writes) to repeat the
2022 1) Storing the write state of each job
2037 fio is running as a server backend, it will send the job states back
2075 To load store write state, read verification job file must contain