Archives of the TeradataForum
Message Posted: Wed, 03 Jan 2007 @ 11:18:18 GMT
What you are doing sounds like a fairly standard approach.
The change to the resource partition weight will have an immediate impact, but only if there is work active within the allocation groups that belong to that resource partition. Resource partition weight is a factor in calculating the relative weight of the active allocation groups, and this calculation is happening more or less in real time. If the resource partition is inactive at the time of the change, the change will only have an impact when work begins running under the conctrol of the resource partition.
A change to the CPU limit could take up to 60 seconds, sometimes slightly longer, to have its full impact. This assumes you are using the default age interval setting of 60 seconds. If your age interval has been changed to something shorter, then the CPU limit change will be felt sooner. Of course if work running in the resource partition is not consuming enough CPU to be bumping up against the CPU limit at the time of the change, then making the change may have no impact at all at that time, and will only be felt if CPU demand should try to exceed the limit.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|