On Fri, Oct 30, 2009 at 2:53 PM, Marty Zimelis <[email protected]> wrote:
> One final note: Just because a virtual machine has QUICKDSP set doesn't > mean it will receive sufficient resources. That's controlled by the SHARE > settings assigned to the various virtual machines in the Dispatch List. And > a discussion of SHARE values is a whole different animal. And the combination of both also has some interesting implications with Linux. By allowing everyone immediately on the dispatch list, the value of your share changes (this is why we call it *relative* share). When you introduce some extra delay (to let CP at least think about the request for a moment) you improve their behavior. The full rationale is too much for a friday, so I'd rather stick with analogies. When you give people immediately what they ask for, they will come back more often. Our secretary at one point decided she would be only handing out office supplies between 9:00 and 10:00. It greatly reduced her overhead (and also a little bit the amount of supplies consumed by the department). Same for polling Linux guests: when they really have something to do, it will be still there after 100 ms and you hardly notice. I would reserve QUICKDSP for those cases where you know they need just a small amount of resources, and you know that servicing them quick will not increase their demand for resources. Otherwise you're making things worse. Another good reason is when other virtual machines will be waiting on this one, and slowing him down makes everyone wait (CP can't always tell that). Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
