Archives of the TeradataForum

Message Posted: Thu, 02 Oct 2003 @ 17:28:05 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Tom,

Thanks for raising the question below, because it brings up a point about how query or session milestones work that I don't think has been discussed before.

You can change a performance group definition at any time, with active work running under its control. This will cause a change to the priority scheduler definition, which will cause the system.GDO record to be re-written. Any time the system.GDO record is changed, all CPU accumulations, whether at the session or the query level, across all performance groups, are zeroed out. The system.GDO record is the operating system's copy of the current priority settings and exists on each node.

This means that if you issue any schmon command that changes a priority scheduler component, say an allocation group weight in another resource partition, or changes a system level limit, that change will cause all queries under the control of any milestone limit in any performance group to start all over in their accumulations of CPU.

And most definitely, relative weights will be recalculated when the system.GDO record changes, as is continuously happening under normal circumstances.

Thanks, - Carrie

	<Prev	Next>		<<First	<Prev	Next>	Last>>