Appearance
Set vCPU and EBS Quotas
AWS accounts are limited by various quotas. The account you use for Yellowbrick installation may need changes to its vCPU and Elastic Block Storage (EBS) quotas.
vCPU Quota
vCPU quotas allocate sufficient CPUs for several components of a Yellowbrick deployment:
- Compute nodes, as defined when instances are created (and shared among virtual compute clusters)
- Compiler
- Bulk load services
- Shared services
Setting Account Quotas
For a successful installation and performance testing, the correct quotas must be requested beforehand. The given quota defines which AWS services will be shared across all resources, actions and items in your AWS account and will need to be large enough to ensure that Yellowbrick scalability is tested successfully. For more information, see What is Service Quotas?. Yellowbrick recommends requesting the appropriate vCPU quota in the AWS Console:
Resource Type | Quota Name | Navigation in the AWS console | Required Quantity |
---|---|---|---|
Compute | Running on-Demand Standard (A, C, D, H, I, M, R, T, Z) Instances | Service Quotas > AWS Services > Amazon Elastic Compute Cloud (Amazon EC2) | 2000 |
Storage | IOPS for Provisioned IOPS SSD (io1) | Service Quotas > AWS Services > Amazon Elastic Block Store (Amazon EBS) | 300,000 |
Storage | IOPS for Provisioned IOPS SSD (io2) | Service Quotas > AWS Services > Amazon Elastic Block Store (Amazon EBS) | 100,000 |
Storage | IOPS modifications for Provisioned IOPS SSD (io1) | Service Quotas > AWS Services > Amazon Elastic Block Store (Amazon EBS) | 500,000 |
Storage | IOPS modifications for Provisioned IOPS SSD (io2) | Service Quotas > AWS Services > Amazon Elastic Block Store (Amazon EBS) | 100,000 |
Networking | VPC | EC2 > Limits > VPCs | 10 |
Networking | EC2-VPC Elastic IPs | EC2 > Limits > EC2-VPC Elastic IPs | 10 |
For most accounts running and managing a Yellowbrick installation, the quota will need to be increased. Specifically, the quota must allow a corresponding number of EC2 instances per your anticipated configuration of Yellowbrick instances in your VPC, plus a given number of CPUs needed by other Yellowbrick services. To request a quota increase, navigate to the Service Quotas console, select AWS servicesin the navigation pane, select a service, and search for the quota name. For more information, see Requesting a quota increase.
Four hardware instance types are currently available for compute nodes:
- V1:
small-v1
(m5dn.4xlarge
) andlarge-v1
(i3en.metal
) - V2:
small-v2
(i4i.4xlarge
) andlarge-v2
(i4i.32xlarge
)
Note that other hardware instance types are used for other necessary Yellowbrick components and services. See Acquire ODCRs.
Example 1: Small Installation (Standard Shared Services, with V1 compute nodes)
For this small installation example, Standard shared services are being used. If you anticipate creating instances that allocate a total of 4 small compute nodes, your vCPU quota will be 64. For a single data warehouse instance with Standard shared services, your total vCPU quota will be 112.
Yellowbrick Component | AWS Instance Type | Number of vCPUs | Quantity of Instance Types | Total vCPUs |
---|---|---|---|---|
Standard shared services (CDWM) | t3.large | 2 | 2 | 4 |
Monitoring services (observability) | m5.xlarge | 4 | 1 | 4 |
Yellowbrick data warehouse instance | m5d.4xlarge | 16 | 1 | 16 |
Compiler service | m5.2xlarge | 8 | 1 | 8 |
Bulk load service (blksvc ) | m5.2xlarge | 8 | 1 | 8 |
Small compute nodes (V1) | m5dn.4xlarge | 16 | 4 | 64 |
Total: 112 |
Example 2: Large Installation (Scaled Shared Services, with V1 compute nodes)
For this large installation example, Scaled shared services are used. This example has 1 instance.
If you anticipate creating instances that allocate a total of 10 large compute nodes, your vCPU quota will be 960, and if you anticipate creating instances that allocate a total of 20 small compute nodes, your vCPU quota will be an additional 320. In addition to the shared services and Yellowbrick instances, your total vCPU quota will be roughly 1600, as shown in the following table:
Yellowbrick Component | AWS Hardware Instance Type | Number of vCPUs | Quantity of Instance Types | Total vCPUs |
---|---|---|---|---|
Scaled shared services (CDWM) | t3.xlarge | 4 | 2 | 8 |
Monitoring services (observability) | m5.8xlarge | 32 | 1 | 32 |
Yellowbrick data warehouse instance | m5dn.12xlarge | 48 | 1 | 48 |
Compiler service | m5.8xlarge | 32 | 1 | 32 |
Bulk load service (blksvc ) | c5n.9xlarge | 36 | 5 | 180 |
Large compute nodes (V1) | i3en.metal | 96 | 10 | 960 |
Small compute nodes (V1) | m5dn.4xlarge | 16 | 20 | 320 |
Total: 1580 |
Example 3: Large Installation (Scaled Shared Services, 1 instance with V2 compute nodes)
The following example is very similar to the previous one, but makes use of the larger V2 compute nodes, which increases the vCPU quota to about 2000:
Yellowbrick Component | AWS Hardware Instance Type | Number of vCPUs | Quantity of Instance Types | Total vCPUs |
---|---|---|---|---|
Scaled shared services (CDWM) | t3.xlarge | 4 | 2 | 8 |
Monitoring services (observability) | m5.8xlarge | 32 | 1 | 32 |
Yellowbrick data warehouse instance | m5dn.12xlarge | 48 | 1 | 48 |
Compiler service | m5.8xlarge | 32 | 1 | 32 |
Bulk load service (blksvc ) | c5n.9xlarge | 36 | 5 | 180 |
Large compute nodes (V2) | i4i.32xlarge | 128 | 10 | 1280 |
Small compute nodes (V2) | i4i.4xlarge | 16 | 20 | 320 |
Total: 1900 |
EBS Quota
Set the appropriate Elastic Block Storage (EBS) quota for the permanent storage volumes of each Yellowbrick instance. Each Yellowbrick instance has two EBS volumes, using a default storage class of gp2
.
- Shared services for the instance require about .32TB
- A Yellowbrick instance requires about 0.4TB
Parent topic:Preparing for a New Installation