Archives of the TeradataForum
Message Posted: Tue, 21 Jan 2003 @ 14:36:26 GMT
You need to keep in mind that the time recorded in AMPUSAGE for the interval expressed by your account string expansion is the (cpu) time required for the unit of work which began in that interval. More simply, if you started a query on a session at noon today, and the query ran for 4 (wall clock) hours, you'll have roughly 4 hours of time accounted for in your ampusage rows for that query alone. That'll make the ampusage for noon today look roughly like your're running at 400% of capacity!
I usually interpret these anomalies as meaning that work is "spilling over" into subsequent intervals and when this happens frequently, it often means that you've got a cpu bottleneck brewing that may need to be addressed.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|