如何解释fio iops日志文件?(how fio iops logfiles are interpreted?)

编程入门 行业动态 更新时间:2024-10-27 14:33:30
如何解释fio iops日志文件?(how fio iops logfiles are interpreted?)

我使用fio进行存储基准测试,使用fio2gnuplot绘制图形,每次运行测试并查看iops的日志文件时,第二个coloumn始终为1,即iops值,由于此图形只是垂直于Y轴的直线。这没有任何意义。 我试过各种iodepths,ioengines但没有用。我使用任何参数(选项)错了吗?

以下是我的工作文件。

[global] enter code here rw=randwrite size=128m thread=1 iodepth=2 ioengine=libaio per_job_logs=0 directory=/home/fio [job_512] write_bw_log=logfiles_libaio/fio-test_512 write_iops_log=logfiles_libaio/fio-test_512 write_lat_log=logfiles_libaio/fio-test_512 bs=512b

这是日志文件

1, 1, 0, 512 2, 1, 1, 512 18, 1, 1, 512 19, 1, 0, 512 31, 1, 1, 512 53, 1, 1, 512 55, 1, 1, 512 56, 1, 0, 512 59, 1, 1, 512 63, 1, 1, 512

I am using fio for storage benchmarking and fio2gnuplot for plotting graphs, every time I run a test and look into logfiles of iops, second coloumn is always 1 which is iops value and due to this graphs are just a straight line perpendicular to Y axis .Which makes no sense. I tried various iodepths,ioengines but no use.am I using any parameters(options)wrong?

following is my jobfile.

[global] enter code here rw=randwrite size=128m thread=1 iodepth=2 ioengine=libaio per_job_logs=0 directory=/home/fio [job_512] write_bw_log=logfiles_libaio/fio-test_512 write_iops_log=logfiles_libaio/fio-test_512 write_lat_log=logfiles_libaio/fio-test_512 bs=512b

and this is the logfile

1, 1, 0, 512 2, 1, 1, 512 18, 1, 1, 512 19, 1, 0, 512 31, 1, 1, 512 53, 1, 1, 512 55, 1, 1, 512 56, 1, 0, 512 59, 1, 1, 512 63, 1, 1, 512

最满意答案

根据fio手册(man fio),在“FIO FILE FORMATS”下,它说:

Fio supports a variety of log file formats, for logging latencies, bandwidth, and IOPS. The logs share a common format, which looks like this: time (msec), value, data direction, offset Time for the log entry is always in milliseconds. The value logged depends on the type of log, it will be one of the following: Latency log Value is in latency in usecs Bandwidth log Value is in KB/sec IOPS log Value is in IOPS Data direction is one of the following: 0 IO is a READ 1 IO is a WRITE 2 IO is a TRIM

但是,我认为'offset'应该是'IO size'。

所以,在你的带宽情况下,它是:

timestamp(ms), bandwidth(KB/sec), R/W, size

According to fio manual(man fio), under "FIO FILE FORMATS", it says:

Fio supports a variety of log file formats, for logging latencies, bandwidth, and IOPS. The logs share a common format, which looks like this: time (msec), value, data direction, offset Time for the log entry is always in milliseconds. The value logged depends on the type of log, it will be one of the following: Latency log Value is in latency in usecs Bandwidth log Value is in KB/sec IOPS log Value is in IOPS Data direction is one of the following: 0 IO is a READ 1 IO is a WRITE 2 IO is a TRIM

However, I think the 'offset' should be 'IO size'.

So, in your bandwidth case, it's:

timestamp(ms), bandwidth(KB/sec), R/W, size

更多推荐

本文发布于:2023-07-29 20:47:00,感谢您对本站的认可!
本文链接:https://www.elefans.com/category/jswz/34/1319612.html
版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。
本文标签:文件   日志   iops   fio   logfiles

发布评论

评论列表 (有 0 条评论)
草根站长

>www.elefans.com

编程频道|电子爱好者 - 技术资讯及电子产品介绍!