Quantcast
Channel: Teradata Developer Exchange - Blog activity for carrie's blog
Viewing all articles
Browse latest Browse all 1058

Simplifying AMP Worker Task Monitoring and Getting it Right - comment () by carrie

$
0
0
Almost, but not quite, so let me try to clear this up for you. (I think you meant "WorkOne", right?) "WorkOne=140" represents the sum of all AMP worker tasks in-use counts for each collect interval within the logging interval. The collect interval is 60 seconds, the logging interval is 600 seconds. A snapshot of how many AMP worker tasks are being used by that work type (WorkOne in this case) at the end of each collect interval is taken. With each succeeding 60-second collect interval, that in-use count number grows, and what appears in the SAWT output is that sum at the end of the logging interval of all those different point-in-time snapshots. This is not "work accomplished" or "CPU time," it is a number of in-use count snapshots accumulated over time. In the adjusted example, "WorkOne = 14.0" represents an average in-use count for that worktype across that logging interval of 600 seconds. It does not represent work done. It represents what the average number of AMP worker tasks that were being used by that worktype for the entire logging interval. Thanks, -Carrie

Viewing all articles
Browse latest Browse all 1058

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>