1 Answer
- Newest
- Most votes
- Most comments
0
To replace the Serverless v2 instances with fixed instances, you'll need to find the appropriate instance types that can match the resource requirements of your workloads. Here's a general approach you can take:
Analyze the Resource Utilization: Based on the information you provided, for the first group of 4 instances (0.5 - 6 ACUs), the CPU is always between 50% and 75%, and the free memory is between 4 and 7 GB. This gives you a good starting point to determine the appropriate instance type.
Choose the Instance Family: Considering the CPU and memory requirements, you could look at instance families like M6g, R6g, or C6g, which are powered by AWS Graviton2 processors and offer a good balance of compute, memory, and cost-effectiveness.
Determine the Instance Size: To match the resource requirements, you could consider the following instance types:
For the first group (0.5 - 6 ACUs):
m6g.medium or r6g.medium instances, which have 2 vCPUs and 8 GB of memory
For the second and third groups (0.5 - 4 ACUs):
m6g.small or r6g.small instances, which have 2 vCPUs and 4 GB of memory
For the fourth group (0.5 - 5.5 ACUs):
m6g.medium or r6g.medium instances, which have 2 vCPUs and 8 GB of memory
Evaluate the Cost Savings: Compare the estimated monthly cost of the fixed instances with the current Serverless v2 instances. The Graviton2-based instances (m6g, r6g, c6g) are generally more cost-effective than the x86-based instances, so you may see significant savings by moving to fixed instances.
Consider Scaling and Availability: Evaluate the scaling and availability requirements of your workloads. Fixed instances may provide more predictable performance, but you'll need to ensure that you have the right number of instances provisioned to handle your workloads.
Test and Optimize: Conduct load testing and performance evaluation with the fixed instances to ensure they can adequately handle your workloads. Adjust the instance types or the number of instances as needed based on the test results.
Keep in mind that the specific instance types and sizes may vary depending on your workload characteristics, availability requirements, and any other specific needs. It's recommended to conduct thorough testing and evaluation before making the final instance selection and migration.
answered 2 months ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago