RIO 02 Teradata Architecture

8/13/2019 RIO 02 Teradata Architecture

1/15


2/15

About the Author

Created By:

Credential

Information:

Version and

Date:

Sudeshna Pal(200271) , Sarnava Das(247258)

Teradata Certified Professional V12. Worked in Teradata Technologies for

last 2.5 years.

V 1.0

Date12/27/2012

2


3/15

Icons Used

Questions

Demonstration

Hands on

Exercise

Coding

Standards

Best Practices

& Industry

Standards

Tools

3

Case StudyTest Your

Understanding

Workshop


4/15

Introduction:

Overview of Teradata 13 Architecture includes:

Parsing Engine (PE)

Access Module Processor (AMP) BYNET

Context Setting: Overview

4


5/15

After completing this chapter you will be able to:

The theory of Parallelism

Perfect Plan generation for query execution.

Shared Nothing Architecture

Objectives

5


6/15

Parsing Engine(PE) is the first level where an user gets connected to, whenever they

login.

It also checks whether the particular user has the privilege to execute a query or not.

Hence Security checkup is one of the key features of PE.

In case the request is coming from IBM Mainframe, PE converts it from EBCDIC to ASCII

format.

Once login is successful and a query is executed, PE creates a plan and informs AMP to

get that executed in the most optimized way. Hence PE is also known as Optimizer.

PE knows the detailed underlying design i.e. the number of AMPs connected, the

number of rows in each table etc, which help making the optimized plan.

Parsing Engine

6


7/15

AMPs are connected to PE via BYNET. They perform all the instructions sent by PE and

send the output back to PE.

Individual AMP has got their individual disk attached to them, where they have read

and write access to perform various queries. Hence Shared Nothing Architecture

comes into play.

All the AMPs distribute rows of the table evenly among themselves. Therefore, while

executing a query all the AMPs work simultaneously and read the records from its own

disks. This feature is called Parallelism.

For IBM mainframe, it converts ASCII returned data to EBCDIC and send back to PE.

In Teradata 13, the AMP Worker Task (AWT) per AMP is increased for better

performance.

Access Module Processor (AMP)

7


8/15

BYNET connects PE and AMP for passing various instructions and corresponding

outputs.

In Teradata system, there are two BYNET systems viz. BYNET 0 and BYNET 1. This is

because, in case one BYNET fails, the other one carries the instruction. It also fastens

communication and hence enhances query performance.

Each BYNET provides bandwidth of 10 Megabytes (MB) per second with Version 1 and

60 MB per second with Version 2. This speed increases linearly as more nodes are

added.

Message Passing Layer (BYNET)

8


9/15

Teradata Architecture (DiagramaticRepresentation)

9


10/15

Questions

10


11/15

Welcome Break

11


12/15

Questions:

1. What is the function performed by BYNET?

2. How many BYNET systems are there in Teradata? Explain theirfunctionalities.

Test Your Understanding

12


13/15

The chapters give a detailed overview of the following processes in Teradata:

The PE checks the syntax of the query, also checks the security right of the user

accessing.

The PE comes up with the best optimized plan for execution of the query.

The PE passes this plan through BYNET to AMP. The AMPs follow the plan to retrieve data from its DISKS.

The AMP passes the data to PE through BYNET.

The PE then passes the data to the user.

Summary

13


14/15

www.teradataforum.com

www.teradata.com

Source

14

Disclaimer: Parts of the content of this course is based on the materials available from the Web sites and books

listed above. The materials that can be accessed from linked sites are not maintained by Cognizant Academy and

we are not responsible for the contents thereof. All trademarks, service marks, and trade names in this course are

the marks of the respective owner(s).
http://www.teradataforum.com/http://www.teradata.com/http://www.teradata.com/http://www.teradataforum.com/


15/15

TD Architecture and access methods

You have successfully completed -

TD Architecture and access methods

RIO 02 Teradata Architecture

Documents

Transcript of RIO 02 Teradata Architecture