Andrea Righi wrote: > A more complicated issue is how to evaluate the total IO bandwidth of a > generic device. We can use some kind of averaging/prediction, but > basically it would be inaccurate due to the mechanic of disks (head > seeks, but also caching, buffering mechanisms implemented directly into > the device, etc.). It's a hard problem. And the same problem exists also > for proportional bandwidth as well, in terms of IO rate predictability I > mean. Actually it's a little-known easy problem. The capacity planning community does it all the time, but then describes it in terms that are only interesting (intelligible?) to an enthusiastic amateur mathematician (;-)) One finds the point, called N*, at which the throughput flattens out and and the response time starts to grow without bounds, and calls that level the maximum. In practice, one does an easier variant. One sets a response-time limit and throttles *everyone* proportionally when th disk starts to regularly degrade beyond the limit. Interestingly, because we're slowing the application to prevent slowing the disks, the value we pick needn't be terribly precise. It also doesn't require any pre- knowledge about the disks. Send me a note if you want to discuss this in more detail. --dave -- David Collier-Brown | Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest davecb@xxxxxxx | -- Mark Twain cell: (647) 833-9377, bridge: (877) 385-4099 code: 506 9191# _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
