Skip to content

fix(website): Reduce Cloud Run memory allocation to 1024Mi#797

Merged
yamadashy merged 1 commit intomainfrom
feat/website-memory
Aug 23, 2025
Merged

fix(website): Reduce Cloud Run memory allocation to 1024Mi#797
yamadashy merged 1 commit intomainfrom
feat/website-memory

Conversation

@yamadashy
Copy link
Owner

This PR reduces the memory allocation for the website server Cloud Run deployment from 2048Mi to 1024Mi to optimize resource usage and reduce costs.

The website server should work efficiently with 1024Mi of memory, and this change will help reduce infrastructure costs without affecting performance.

Checklist

  • Run npm run test
  • Run npm run lint

Reduce memory allocation from 2048Mi to 1024Mi to optimize resource usage
and costs for the website server deployment.
Copilot AI review requested due to automatic review settings August 23, 2025 04:47
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 23, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Reduces the Cloud Run memory allocation in the Deploy to Cloud Run step of website/server/cloudbuild.yaml from 2048Mi to 1024Mi. No other fields are changed.

Changes

Cohort / File(s) Summary
Cloud Run deployment config
website/server/cloudbuild.yaml
In the deploy step, the memory flag was updated from 2048Mi to 1024Mi; all other deploy options remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a86df65 and db4375f.

📒 Files selected for processing (1)
  • website/server/cloudbuild.yaml (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/website-memory

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @yamadashy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on optimizing the resource allocation for the website server's Cloud Run deployment. The primary goal is to reduce operational costs by decreasing the memory allocated to the server, while ensuring that the website's performance remains unaffected. This change is a strategic step towards more efficient infrastructure management.

Highlights

  • Cloud Run Memory Allocation: The memory allocated to the website server's Cloud Run deployment has been reduced from 2048Mi to 1024Mi.
  • Cost Optimization: This adjustment is aimed at optimizing resource usage and reducing infrastructure costs associated with the website server.
  • Performance Expectation: The website server is expected to continue operating efficiently with the reduced memory, ensuring no impact on performance.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@claude
Copy link
Contributor

claude bot commented Aug 23, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

@yamadashy yamadashy merged commit 5e6918f into main Aug 23, 2025
50 of 52 checks passed
@yamadashy yamadashy deleted the feat/website-memory branch August 23, 2025 04:47
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request reduces the memory allocation for the Cloud Run service from 2048Mi to 1024Mi to optimize costs. The change is straightforward and aligns with the goal of resource optimization. I've added a suggestion to also consider reducing the CPU allocation from 2 to 1, which could provide additional cost savings if the application's performance profile allows for it. Overall, this is a good infrastructure tuning effort.

- '2048Mi'
- '1024Mi'
- '--cpu'
- '2'
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

With the memory being reduced to 1024Mi, the 2 vCPUs might be underutilized, especially since Node.js applications are typically single-threaded. To further optimize costs, consider reducing the CPU allocation to 1. This would align resource allocation more closely and could reduce costs without impacting performance, assuming the application is not CPU-bound.

      - '1'

@codecov
Copy link

codecov bot commented Aug 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.49%. Comparing base (a86df65) to head (db4375f).
⚠️ Report is 86 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #797   +/-   ##
=======================================
  Coverage   87.49%   87.49%           
=======================================
  Files         113      113           
  Lines        6437     6437           
  Branches     1316     1316           
=======================================
  Hits         5632     5632           
  Misses        805      805           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant