• You can support future updates of this package Click to Donate
  • Version
  • Download 1
  • File Size 2.24 MB
  • File Count 1
  • Create Date May 29, 2023
  • Last Updated May 29, 2023
  • Installation Support and Update requests /forums/topic/fio
  • TOS4 x86_64 request fio TOS4 x86_64
fio TOS5 x86_64.tpk

Persistent disk performance benchmarks (CLI)


Applicable models: x.64 series
Applicable TOS4: 4.1.27 or later versions - on request
Applicable TOS5: 5.1.12 or later versions

Required packages:

App WebUI for additional settings can be accesses at:

TOS4: http(s)://yournasip:port/modules/OwnTone/www
TOS5: click on Support & Help from app description inside the App Center

Running fio is normally the easiest part - you just give it the job file (or job files) as parameters:

$ fio [options] [jobfile] ...

and it will start doing what the jobfile tells it to do. You can give more than one job file on the command line, fio will serialize the running of those files. Internally that is the same as using the :option:`stonewall` parameter described in the parameter section.

If the job file contains only one job, you may as well just give the parameters on the command line. The command line parameters are identical to the job parameters, with a few extra that control global parameters. For example, for the job file parameter :option:`iodepth=2 <iodepth>`, the mirror command line option would be :option:`--iodepth 2 <iodepth>` or :option:`--iodepth=2 <iodepth>`. You can also use the command line for giving more than one job entry. For each :option:`--name <name>` option that fio sees, it will start a new job with that name. Command line entries following a :option:`--name <name>` entry will apply to that job, until there are no more entries or a new :option:`--name <name>` entry is seen. This is similar to the job file options, where each option applies to the current job until a new [] job entry is seen.

User Reviews
You are not allowed to post review.