Skip to content

feat(website): Reduce Cloud Run CPU allocation from 2 to 1 #809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamadashy merged 1 commit into from
Aug 26, 2025
Merged

feat(website): Reduce Cloud Run CPU allocation from 2 to 1 #809

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/server/cloudbuild.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ steps:
- '--memory'
- '1024Mi'
- '--cpu'
- '2'
- '1'
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Aug 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Halving the CPU allocation from 2 to 1 is a significant change that introduces a risk of performance degradation, potentially leading to increased request latency or timeouts under heavy load. A change of this nature should be supported by performance testing data to ensure service level objectives (SLOs) can still be met. I strongly recommend either conducting load tests to validate this change before merging or implementing enhanced monitoring of CPU utilization, instance count, and request latency (p95/p99) immediately following deployment to quickly detect and mitigate any negative impact on performance.

- '--min-instances'
- '0'
- '--max-instances'
Expand Down
Loading