Responding Sessions

Database
Highlighted
Enthusiast

Responding Sessions

Hi all, 

 

We are on teradata 16.10.I observed that the responding sessions are showing impact CPU in viewpoint .

 

I always thought that responding sessions doesnt use any CPU/IO .But its showing IMPACT CPU .Does this mean the session using lot of CPU ?

 

Immediate response is appreciated .

 

thanks,


Accepted Solutions
Senior Apprentice

Re: Responding Sessions

No, I'm not aware of any documentation that supports this view.

 

As you're probably aware, once the request reaches Responding state then the final answer set has been built in it's entirety, the AMPs have completed their AMP local sort (if required) and only the Bynet sort/merge is left (and I'm almost certain that the Bynet work is not recorded anywhere against the individual query).

 

Basically, once the query reaches this state then there is nothing left for the AMPs to do.

 

Cheers,

Dave

Ward Analytics Ltd - information in motion
www: http://www.ward-analytics.com
1 ACCEPTED SOLUTION
4 REPLIES 4
Senior Apprentice

Re: Responding Sessions

Hi,

 

I doubt it very much. The Impact CPU value that is shown is probably from when the request was Active (i.e. processing) and not from the response processing.

 

HTH

Dave

Ward Analytics Ltd - information in motion
www: http://www.ward-analytics.com
Enthusiast

Re: Responding Sessions

Thank you Dave ..I too felt the same .Do you know any documentation that supports the same ?

The below is from the viewpoint .

 

responding.PNG

Teradata Employee

Re: Responding Sessions

For TD15.10 and later, the Impact CPU value shown in Viewpoint is calculated at the request level (so the "cumulative" value for the most recent request is displayed for responding sessions). For TD15.0 and earlier, it was calculated from the most recent snapshot (so was zero / blank for responding sessions).

Senior Apprentice

Re: Responding Sessions

No, I'm not aware of any documentation that supports this view.

 

As you're probably aware, once the request reaches Responding state then the final answer set has been built in it's entirety, the AMPs have completed their AMP local sort (if required) and only the Bynet sort/merge is left (and I'm almost certain that the Bynet work is not recorded anywhere against the individual query).

 

Basically, once the query reaches this state then there is nothing left for the AMPs to do.

 

Cheers,

Dave

Ward Analytics Ltd - information in motion
www: http://www.ward-analytics.com