Iops » История » Версия 7
Андрей Волков, 2012-05-25 19:04
| 1 | 3 | Андрей Волков | h1. IOPS (Input/Output Operations Per Second) |
|---|---|---|---|
| 2 | 1 | Андрей Волков | |
| 3 | Отличная подборка для понимания показателя IOPS: |
||
| 4 | http://en.wikipedia.org/wiki/IOPS |
||
| 5 | 4 | Андрей Волков | |
| 6 | Утилита тестирования (gentoo): |
||
| 7 | sys-block/fio-2.0.7:0::ekb-info |
||
| 8 | 5 | Андрей Волков | |
| 9 | IOPS в QEMU-KVM |
||
| 10 | http://wiki.qemu.org/Features/VirtioIoeventfd |
||
| 11 | 6 | Андрей Волков | |
| 12 | DiskIOLimits в QEMU-KVM еще не готов: |
||
| 13 | 1 | Андрей Волков | http://wiki.qemu.org/Features/DiskIOLimits |
| 14 | 7 | Андрей Волков | |
| 15 | *Background* |
||
| 16 | |||
| 17 | When several instances of QEMU are running they can interfere with system performance through excessive disk I/O. Sometimes it is desirable to limit disk I/O in order to keep QEMU from affecting other applications or instances. |
||
| 18 | |||
| 19 | The availability of disk I/O throttling depends on the underlying storage (image file, LVM, NFS, Ceph). On Linux the cgroups blkio-controller supports I/O throttling on block devices but is a relatively recent feature. More importantly, there is no single mechanism for disk I/O throttling across all underlying storage types and for some types there is no way to throttle at all. |
||
| 20 | |||
| 21 | The disk I/O limits feature introduces QEMU block layer I/O limits together with command-line and QMP interfaces for configuring limits. This allows I/O limits to be imposed across all underlying storage types using a single interface. |