Teradata architechtural behaviour

Database

Teradata architechtural behaviour

Hi all,

I would like to know that in which specific scenarios, an AMP will be overloaded

- for example, while firing an untuned query, how would this SQL be submitted to the AMPs and how the AMPs would respond to this untuned query.

Kindly let me know the conceptual phenomena taking place.

Regards,

Soumik

Tags (1)
3 REPLIES

Re: Teradata architechtural behaviour

Hi,

Yes, you can think it that way when we have skewness, with respect to data volume, uneven distribution  due to bad choice of PI, bad joins etc.But Teradata system is built for parallelism from scratch and we have to make use of its capabilities.

Maybe you can  read about AWT(Amp worker task) to see more into the architecture.

Work00-- Query step coming from dispatcher

Work01-- First level of spawned work

 and the standard reserve pools( 24 reserved AWTs on each amp)

Cheers,

Raja

Re: Teradata architechtural behaviour

Thanks a tonne Raja!

Could you please provide me a link for such document, so that it can be more understandable to me?

Regards,

Soumik

Re: Teradata architechtural behaviour

Hi Soumik,

For AWT,

you can have a look at this link http://developer.teradata.com/blog/carrie/2010/12/how-to-calculate-your-max-number-of-usable-amp-wor... .  Carrie has given a vivid description  and clarifying many queries.

Cheers,

Raja