大网数据广告活动
服务器运维问答

IOPs Comparison and Block Size

· 52CE 我爱测

As long as I know - IOps is a IO operations per second on a given data block. But size of that given block if often omitted. I assume, that block size does not make difference as long as its relatively small and I can compare iop…

问题原文

原帖链接 · Vasilly.Prokopyev · CC BY-SA 3.0

As long as I know - IOps is a IO operations per second on a given data block. But size of that given block if often omitted.

I assume, that block size does not make difference as long as its relatively small and I can compare iops requirements for some software with iops performance of a storage system given by the manufacturer. Am I right?

And where is a limit for block size to be relatively small? Is 32k, for example, already too large?

已采纳解答

原帖链接 · user121391 · CC BY-SA 3.0

Best block size depends on your application and use pattern. In general sequential access profits from large blocks (less reads needed), random access from small blocks (less wasted partial reads), but that is not set in stone.

Straight IOPS comparisons are mostly a marketing strategy/advertisement, if the test circumstances are not completely made public or specific versions of comparison tools are used. You have to fix the variables that do not interest you and then compare the results. I think it is difficult to reproduce all test settings that potential customers would need, and also if you publish everything, your competitor might cheat and compare his best results to your worst, so they just publish either best or average scores.

Usual block sizes are from 512 B to 128 KB, but the limits depend on the used file system, operating system and application software.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-11-02)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。