fio测试工具详尽文档（3.6版）：从入门到高级用法详解

需积分: 48 147 浏览量更新于2024-07-18 2 收藏 381KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"FIO是一个灵活的I/O测试工具，版本为3.6-39-gcf04-dirty，发布日期为2018年5月28日。这个文档详细介绍了FIO的各个方面，包括概述、历史、源码获取、邮件列表、作者信息以及软件包安装、构建方法等。对于想要深入了解如何使用FIO进行存储性能测试的人来说，这是极其宝贵的资源。 1.1 **概述与历史**：文档首先简要介绍了FIO的背景和它在I/O性能测试领域的角色，以及它的发展历程，帮助用户了解工具的核心价值和变迁。 1.2 **源码**：文档指出了获取FIO源代码的途径，这对于开发者和自定义编译者来说是关键信息。 1.3 **邮件列表**：提供了FIO社区的支持平台，用户可以在这里提问、分享经验或报告问题。 1.4 **作者**：文档提到了主要开发者或维护者的名字，以便于用户联系或致谢。 1.5 **软件包**：包括了Windows和其他平台的预编译二进制包，便于不同操作系统上的快速部署。 1.6 **构建**： - **Windows**：针对Windows用户的构建指南，可能包括特定的依赖和配置步骤。 - **文档**：强调了文档的重要性，可能是关于构建过程中的注意事项或文档更新。 1.7 **平台支持**：说明了FIO兼容的硬件和操作系统环境，确保用户知道他们的系统是否适用。 1.8 **运行FIO**：这部分详细解释了如何启动和执行测试，包括基本命令行结构和选项设置。 1.9 **工作原理**：解释了FIO是如何模拟真实的I/O场景，以及它如何测量和报告性能指标。 1.10 **命令行选项**：列出了所有可调整的参数，用户可以根据需求定制测试条件。 1.11 **Job文件格式**：介绍Job文件的结构，这是一种配置文件，用于指定测试的工作负载和参数，对高级用户尤其重要。 1.12 **Job文件参数**： - **参数类型**：说明参数的不同类型及其含义。 - **单位**：解释了各个参数的单位，确保用户理解测试结果的上下文。 - **工作描述**：如何描述任务的具体操作，如读写、随机/顺序等。 - **时间相关参数**：涉及延迟、速率、吞吐量等与时间相关的测量指标。 - **文件目标/设备**：指定测试的数据存储位置。 - **I/O类型**：区分不同的I/O操作模式，如随机读写、顺序读写等。 - **块大小**：影响I/O操作的基本数据单元。 - **缓冲与内存**：涉及缓存策略和内存管理。 - **I/O大小**：控制单次I/O请求的数据量。 - **I/O引擎**：选择不同类型的I/O处理机制。 - **引擎特定参数**：针对特定引擎的额外设置。 - **I/O深度**：并行I/O请求的数量。 - **I/O速率**：设定理论上的数据传输速度。 - **I/O延迟**：测量I/O操作的时间消耗。 - **I/O回放**：利用已有的I/O序列进行测试。 - **线程、进程与同步**：涉及并发执行和同步策略。 - **验证**：确保测试的准确性和一致性。 - **稳态测试**：长期运行以观察性能稳定性。 - **测量与报告**：如何解析和分析测试结果。 - **错误处理**：描述了遇到问题时的错误检测和处理机制。 1.13 **预定义工作负载**：介绍如何使用预设的工作负载模板简化测试配置。这份文档是FIO工具的详尽指南，涵盖了从安装到使用的全过程，以及深入的内部机制和参数解释，对于优化存储性能、评估设备性能或学习I/O测试原理都极具价值。"

资源详情

资源推荐

ﬁo Documentation, Release 3.6-39-gcf04-dirty

--max-jobs=nr

Set the maximum number of threads/processes to support to nr. NOTE: On Linux, it may be necessary to

increase the shared-memory limit (/proc/sys/kernel/shmmax) if ﬁo runs into errors while creating jobs.

--server=args

Start a backend server, with args specifying what to listen to. See Client/Server section.

--daemonize=pidfile

Background a ﬁo server, writing the pid to the given pidﬁle ﬁle.

--client=hostname

Instead of running the jobs locally, send and run them on the given hostname or set of hostnames. See

Client/Server section.

--remote-config=file

Tell ﬁo server to load this local ﬁle.

--idle-prof=option

Report CPU idleness. option is one of the following:

calibrate Run unit work calibration only and exit.

system Show aggregate system idleness and unit work.

percpu As system but also show per CPU idleness.

--inflate-log=log

Inﬂate and output compressed log.

--trigger-file=file

Execute trigger command when ﬁle exists.

--trigger-timeout=time

Execute trigger at this time.

--trigger=command

Set this command as local trigger.

--trigger-remote=command

Set this command as remote trigger.

--aux-path=path

Use this path for ﬁo state generated ﬁles.

Any parameters following the options will be assumed to be job ﬁles, unless they match a job ﬁle parameter. Multiple

job ﬁles can be listed and each job ﬁle will be regarded as a separate group. Fio will stonewall execution between

each group.

1.11 Job ﬁle format

As previously described, ﬁo accepts one or more job ﬁles describing what it is supposed to do. The job ﬁle format is

the classic ini ﬁle, where the names enclosed in [] brackets deﬁne the job name. You are free to use any ASCII name

you want, except global which has special meaning. Following the job name is a sequence of zero or more parameters,

one per line, that deﬁne the behavior of the job. If the ﬁrst character in a line is a ‘;’ or a ‘#’, the entire line is discarded

as a comment.

A global section sets defaults for the jobs described in that ﬁle. A job may override a global section parameter, and a

job ﬁle may even have several global sections if so desired. A job is only affected by a global section residing above

it.

10 Chapter 1. ﬁo - Flexible I/O tester rev. 3.6

ﬁo Documentation, Release 3.6-39-gcf04-dirty

The --cmdhelp option also lists all options. If used with a command argument, --cmdhelp will detail the given

command.

See the examples/ directory for inspiration on how to write job ﬁles. Note the copyright and license requirements

currently apply to examples/ ﬁles.

So let’s look at a really simple job ﬁle that deﬁnes two processes, each randomly reading from a 128MiB ﬁle:

; -- start job file --

[global]

rw=randread

size=128m

[job1]

[job2]

; -- end job file --

As you can see, the job ﬁle sections themselves are empty as all the described parameters are shared. As no filename

option is given, ﬁo makes up a ﬁlename for each of the jobs as it sees ﬁt. On the command line, this job would look as

follows:

$ fio --name=global --rw=randread --size=128m --name=job1 --name=job2

Let’s look at an example that has a number of processes writing randomly to ﬁles:

; -- start job file --

[random-writers]

ioengine=libaio

iodepth=4

rw=randwrite

bs=32k

direct=0

size=64m

numjobs=4

; -- end job file --

Here we have no global section, as we only have one job deﬁned anyway. We want to use async I/O here, with a depth

of 4 for each ﬁle. We also increased the buffer size used to 32KiB and deﬁne numjobs to 4 to fork 4 identical jobs.

The result is 4 processes each randomly writing to their own 64MiB ﬁle. Instead of using the above job ﬁle, you could

have given the parameters on the command line. For this case, you would specify:

$ fio --name=random-writers --ioengine=libaio --iodepth=4 --rw=randwrite --bs=32k --

˓→direct=0 --size=64m --numjobs=4

When ﬁo is utilized as a basis of any reasonably large test suite, it might be desirable to share a set of standard-

ized settings across multiple job ﬁles. Instead of copy/pasting such settings, any section may pull in an external

filename.fio ﬁle with include ﬁlename directive, as in the following example:

; -- start job file including.fio --

[global]

filename=/tmp/test

filesize=1m

include glob-include.fio

[test]

rw=randread

(continues on next page)

1.11. Job ﬁle format 11

ﬁo Documentation, Release 3.6-39-gcf04-dirty

The architecture page size of the running system.

$mb_memory

Megabytes of total memory in the system.

$ncpus

Number of online available CPUs.

These can be used on the command line or in the job ﬁle, and will be automatically substituted with the current system

values when the job is run. Simple math is also supported on these keywords, so you can perform actions like:

size=8

$mb_memory

and get that properly expanded to 8 times the size of memory in the machine.

1.12 Job ﬁle parameters

This section describes in details each parameter associated with a job. Some parameters take an option of a given type,

such as an integer or a string. Anywhere a numeric value is required, an arithmetic expression may be used, provided

it is surrounded by parentheses. Supported operators are:

• addition (+)

• subtraction (-)

• multiplication (*)

• division (/)

• modulus (%)

• exponentiation (^)

For time values in expressions, units are microseconds by default. This is different than for time values not in expres-

sions (not enclosed in parentheses). The following types are used:

1.12.1 Parameter types

str String: A sequence of alphanumeric characters.

time Integer with possible time sufﬁx. Without a unit value is interpreted as seconds unless otherwise speciﬁed.

Accepts a sufﬁx of ‘d’ for days, ‘h’ for hours, ‘m’ for minutes, ‘s’ for seconds, ‘ms’ (or ‘msec’) for milliseconds

and ‘us’ (or ‘usec’) for microseconds. For example, use 10m for 10 minutes.

int Integer. A whole number value, which may contain an integer preﬁx and an integer sufﬁx:

[integer preﬁx] number [integer sufﬁx]

The optional integer preﬁx speciﬁes the number’s base. The default is decimal. 0x speciﬁes hexadecimal.

The optional integer sufﬁx speciﬁes the number’s units, and includes an optional unit preﬁx and an optional

unit. For quantities of data, the default unit is bytes. For quantities of time, the default unit is seconds unless

otherwise speciﬁed.

With kb_base=1000, ﬁo follows international standards for unit preﬁxes. To specify power-of-10 decimal

values deﬁned in the International System of Units (SI):

• K – means kilo (K) or 1000

• M – means mega (M) or 1000**2

1.12. Job ﬁle parameters 13

剩余84页未读，继续阅读

劳注华

粉丝: 0
资源: 3

fio测试工具详尽文档（3.6版）：从入门到高级用法详解

windows下fio安装包

fio-3.8.zip

FIO-master3.5

linux fio测试工具下载

linux中fio工具的使用方法

如何使用fio测试HBA卡的带宽

linx卸载fio工具

如何使用fio测试存储整机的带宽和iops

linux fio工具最新版本

windows的fio测试怎么用

fio性能测试工具新添图形前端gfio

nand读写速度测试手段如fio

linux下怎么安装fio工具

帮我写一个fio测试程序

FIO工具4k随机写

fio测试iops

使用fio测试数据一致性如何检验

FIO测试硬盘都看哪些结果数值

麒麟系统下载FIO工具

编写一个fio测试脚本

最新资源