[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH V7 0/5] Continuous Leaky Bucket Throttling
From: |
Benoît Canet |
Subject: |
Re: [Qemu-devel] [PATCH V7 0/5] Continuous Leaky Bucket Throttling |
Date: |
Thu, 29 Aug 2013 20:01:58 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
> Here is my understanding of how the algorithm works:
>
> There is a "max" burst value which is a guaranteed allowance. If max is
> 100 units then you can always use up to 100 units without being
> throttled.
>
> After the max burst value has been exceeded, requests are throttled down
> to the "avg" rate value. The way it works is like this:
>
> 1. If the max hasn't been reached, allow the request through.
> 2. If the max has been reached, schedule a timer for when the bucket
> level comes back down to max.
> 3. Increment bucket level when the request is allowed through.
> 4. Drain bucket level according to avg rate as time passes.
Another point is that the initial ability to burst replenish when the guest does
not do any I/Os.
One usage of this is compute intensive tasks where slice of time are dedicated
to computations and separated by a flush to disk of the resulting data.
Best regards
Benoît
- [Qemu-devel] [PATCH V7 2/5] throttle: Add units t ests, (continued)
- [Qemu-devel] [PATCH V7 2/5] throttle: Add units t ests, Benoît Canet, 2013/08/28
- [Qemu-devel] [PATCH V7 3/5] block: Enable the new throttling code in the block layer., Benoît Canet, 2013/08/28
- [Qemu-devel] [PATCH V7 4/5] block: Add support fo r throttling burst max in QMP and the command line., Benoît Canet, 2013/08/28
- [Qemu-devel] [PATCH V7 5/5] block: Add iops_siz e to do the iops accounting for a given io size., Benoît Canet, 2013/08/28
- Re: [Qemu-devel] [PATCH V7 0/5] Continuous Leaky Bucket Throttling, Stefan Hajnoczi, 2013/08/29
- Re: [Qemu-devel] [PATCH V7 0/5] Continuous Leaky Bucket Throttling,
Benoît Canet <=