Cloud Run: Right-size market-data service CPU to 1 vCPU - #104
Open
cloud-guardian-sh[bot] wants to merge 1 commit into
Open
Cloud Run: Right-size market-data service CPU to 1 vCPU#104cloud-guardian-sh[bot] wants to merge 1 commit into
cloud-guardian-sh[bot] wants to merge 1 commit into
Conversation
Terraform Plan 馃摑Show PlanNo plan file found
Environment: dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR right-sizes the
market-dataCloud Run service to use 1 vCPU. The violation suggests a reduction to 1 vCPU, indicating that the deployed service is likely configured with higher CPU, or 1 vCPU is the recommended optimal size. This change aligns the IaC with the target 1 vCPU.Changes
google_cloud_run_v2_service.market_dataresource interraform/modules/market-data/main.tfto setcpu = "1"within theresources.limitsblock.Estimated Monthly Savings
Optimizing CPU allocation for Cloud Run services can lead to significant cost reductions. If the service was previously consuming more than 1 vCPU and is now provisioned at 1 vCPU, this change could lead to potential savings. For each 1 vCPU reduced in a continuously running service, estimated monthly savings are approximately $60.