Supported Node Counts | Teradata Vantage on Azure (DIY) - Supported Node Counts - Teradata Vantage on Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide
Product
Teradata Vantage on Azure
Release Number
2.2
Published
August 2021
Language
English (United States)
Last Update
2021-08-06
dita:mapPath
djf1623284042771.ditamap
dita:ditavalPath
fon1623285509395.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
The number of supported nodes you can scale out or in to based on the Base Number of Nodes originally deployed using the solution template. For example, if you originally deployed 8 nodes, you can scale out to 10, 11, 13, 16, 22, or 32. If you scale out from 8 to 16 nodes, you can do either of the following:
  • Scale out again to 22 or 32 nodes.
  • Scale in to 13, 11, 10, or back to the original 8 nodes.

Scaling out is available for base node counts up to 56.

Certain node counts would result in an uneven distribution of amps across the instances and therefore no significant performance benefit. Node counts that would result in increased hardware costs without a corresponding performance benefit are not supported.

If Baseline system was deployed with 12 amps per node (usually the following instances come up with 12 amps -> E16sv3/ E16sv4

Number of Nodes

in Baseline system

 Scale out Increments/Options
2 4  
3 6  
4 8  
5 10  
6 12  
7 14  
8 16  
9 18  
10 20  
11 22  
12 24  
13 26  
14 28  
15 30  
16 32  
17 34  
18 36  
19 38  
20 40  
21 42  
22 44  
23 46  
24 48  
25 50  
26 52  
27 54  
28 56  
29 58  
30 60  
31 62  
32 64  
33    
34    
35    
36    
37    
38    
39    
40    
41    
42    
43    
44    
45    
46    
47    
48    
49    
50    
51    
52    
53    
54    
55    
56    
57    
58    
59    
60    
61    
62    
63    
64    

If Baseline system was deployed with 24 amps per node (usually the following instances come up with 24 amps -> E32sv3/v4, E32-16sv3/v4, E32-8sv3/v4

Number of Nodes in Baseline system Scale out Increments/Options
2 3 4 8
3 4 6 12
4 6 8 16
5 7 10 20
6 8 12 24
7 10 14 28
8 11 16 32
9 12 18 36
10 14 20 40
11 15 22 44
12 16 24 48
13 18 26 52
14 19 28 56
15 20 30 60
16 22 32 64
17 23 34  
18 24 36  
19 26 38  
20 27 40  
21 28 42  
22 30 44  
23 31 46  
24 32 48  
25 34 50  
26 35 52  
27 36 54  
28 38 56  
29 39 58  
30 40 60  
31 42 62  
32 43 64  
33 44    
34 46    
35 47    
36 48    
37 50    
38 51    
39 52    
40 54    
41 55    
42 56    
43 58    
44 59    
45 60    
46 62    
47 63    
48 64    
   

If Baseline system was deployed with 48 amps per node (usually the following instances come up with 48 amps -> E64sv3/v4, E64-32sv3/v4, E64-16sv3/v4 instances

Number of Nodes in Baseline system Scale out Increments/Options
2 3 4 6 8
3 4 5 6 8
4 5 6 7 8
5 6 7 8 10
6 7 8 10 12
7 8 10 12 14
8 10 11 13 16
9 11 12 15 18
10 12 14 16 20
11 13 15 18 22
12 14 16 20 24
13 15 18 21 26
14 16 19 23 28
15 18 20 24 30
16 19 22 26 32
17 20 23 28 34
18 21 24 29 36
19 22 26 31 38
20 23 27 32 40
21 24 28 34 42
22 26 30 36 44
23 27 31 37 46
24 28 32 39 48
25 29 34 40 50
26 30 35 42 52
27 31 36 44 54
28 32 38 45 56
29 34 39 47 58
30 35 40 48 60
31 36 42 50 62
32 37 43 52 64
33 38 44 53  
34 39 46 55  
35 40 47 56  
36 42 48 58  
37 43 50 60  
38 44 51 61  
39 45 52 63  
40 46 54 64  
41 47 55    
42 48 56    
43 50 58    
44 51 59    
45 52 60    
46 53 62    
47 54 63    
48 55 64    
49 56      
50 58      
51 59      
52 60      
53 61      
54 62      
55 63      
56 64      
           

It is very important to understand that the number of AMPS on a given VM type depend on the initial system size i.e. the baseline system. Table as follows:

Azure

VM Type

 AMPs per instance
E16sv3 12
E32sv3 24
E32-16sv3 24
E32-8sv3 24
E64sv3 48
E64-32sv3 48
E64-16sv3 48