You are correct in your basic understanding of how dynamic virtual partitions work. I also agree with you that using the dynamic sharing of resources between virtual partitions is preferable than the fixed approach.
With dynamic virtual partitions, Company Sm can use more CPU than it is allocation percent of 30% entitles it to at any point in time, if Company Bg doesn't have enough work active to consume its allocated 70%. However, as soon as Company Bg has enough active work to use its allocated 70%, it will get that CPU immediately. It won't have to wait for a Company Sm query to complete or even wait a couple of seconds for resources to be moved over.
The SLES 11 priority scheduler is built on the SLES 11 operating system, which immediately adjusts its resource allocations when new work enters the system that is of a higher priority, or that belongs to a previously under-utilizied virtual partition or workload. SLES 11 does accounting and makes resource allocation decisions in the nano-second range, so you can expect that the CPU cycles will become available to the arriving Bg query very close to immediately.
Amit,
You are correct in your basic understanding of how dynamic virtual partitions work. I also agree with you that using the dynamic sharing of resources between virtual partitions is preferable than the fixed approach.
With dynamic virtual partitions, Company Sm can use more CPU than it is allocation percent of 30% entitles it to at any point in time, if Company Bg doesn't have enough work active to consume its allocated 70%. However, as soon as Company Bg has enough active work to use its allocated 70%, it will get that CPU immediately. It won't have to wait for a Company Sm query to complete or even wait a couple of seconds for resources to be moved over.
The SLES 11 priority scheduler is built on the SLES 11 operating system, which immediately adjusts its resource allocations when new work enters the system that is of a higher priority, or that belongs to a previously under-utilizied virtual partition or workload. SLES 11 does accounting and makes resource allocation decisions in the nano-second range, so you can expect that the CPU cycles will become available to the arriving Bg query very close to immediately.
Thanks, -Carrie