qemu/docs/throttle.txt

23 second and the number of operations per second (IOPS). For each one of
24 them the user can set a global limit or separate limits for read and
29 the parameters for both cases:
42 It is possible to set limits for both IOPS and bps at the same time,
43 and for each case we can decide whether to have separate read and
74 user to do bursts of I/O for a configurable amount of time. A burst is
81 I/O they allow. These two can be configured separately for each one of
88 bursts of 2000 IOPS for 60 seconds, we would do it like this (the line
89 is split for clarity):
113 IOPS for 1 minute before it's throttled down to 100 IOPS.
116 long period of time with unused I/O (see below for details).
118 The default value for 'iops-total-max' is 0 and it means that bursts
122 Here's the complete list of parameters for configuring bursts:
151 request for accounting purposes. Larger requests will be counted
154 For example, if iops-size is set to 4096 then an 8KB request will be
247 bucket will start to empty, allowing for bursts again.
252 6000, allowing for 3 more seconds of I/O at 2000 IOPS.
263 graph, allowing for more flexibility.
295 will disappear when -object gains support for structured options and
324 A similar setup can also be done with the command line, for example:
330 filter allows for more complex configurations. For example, let's say
331 that we have three different drives and we want to set I/O limits for
332 each one of them and an additional set of limits for the combined I/O
335 First we would define all throttle groups, one for each one of the
343 Now we can define the drives, and for each one of them we use two