A financial services organization is planning the Google Compute Engine infrastructure for a continuous, memory-intensive risk modeling service that operates 24/7. The application requires 6 vCPUs and 48 GB of RAM to maintain optimal throughput, but cannot tolerate unexpected node shutdowns or terminations. The team wants to ensure high availability while minimizing compute costs over a 3-year production deployment period. Which Compute Engine configuration strategy should you recommend?
- AProvision Spot VMs with a custom machine type of 6 vCPUs and 48 GB of RAM to leverage maximum hourly discounts.
- BProvision standard N2 instances with 8 vCPUs and reliance on automatic Sustained Use Discounts without purchase commitments.
- Provision a custom N2 machine type with 6 vCPUs and 48 GB of RAM, combined with a 3-year Committed Use Discount (CUD) for compute resources.Answer
- DMigrate the risk modeling backend service to Cloud Functions using memory-allocated trigger execution instances.
Answer
Provision a custom N2 machine type configured with 6 vCPUs and 48 GB of RAM, combined with a 3-year Committed Use Discount (CUD).
Configuring a custom machine type allows exact tailoring of vCPUs (6) and RAM (48 GB) to prevent overprovisioning costs. Combining this with a 3-year Committed Use Discount delivers the maximum possible cost reduction for uninterrupted, continuous production workloads.
Step-by-Step Solution
Key Concept
Compute Engine Custom Machine Types and Committed Use Discounts (CUDs)