Ofcourse the random read/write tests arn't particularly realistic for actual workloads. The correct value is going to be dependent on the guest workload rather than the cloud operator. Although I agree that the cloud operator could set the cache value to something much higher than 1MB without any downside?
Regardless shouldn't this be made in to a blueprint as its a feature request rather than a bug? Especially since it could be adding new operator configuration options.
Good summary of the possible performance improvements here:
http:// events. linuxfoundation .org/sites/ events/ files/slides/ p0.pp_. pdf
Ofcourse the random read/write tests arn't particularly realistic for actual workloads. The correct value is going to be dependent on the guest workload rather than the cloud operator. Although I agree that the cloud operator could set the cache value to something much higher than 1MB without any downside?
Regardless shouldn't this be made in to a blueprint as its a feature request rather than a bug? Especially since it could be adding new operator configuration options.