On Mon, Sep 02, 2019 at 05:45:50PM +0200, Paolo Valente wrote: > Thanks for this extra explanations. It is a little bit difficult for > me to understand how the min/max teaks for exactly, but you did give > me the general idea. It just limits how far high and low the IO issue rate, measured in cost, can go. ie. if max is at 200%, the controller won't issue more than twice of what the cost model says 100% is. > Are these results in line with your expectations? If they are, then > I'd like to extend benchmarks to more mixes of workloads. Or should I > try some other QoS configuration first? They aren't. Can you please include the content of io.cost.qos and io.cost.model before each run? Note that partial writes to subset of parameters don't clear other parameters. Thanks. -- tejun
