docs: 32 cores for bridge nodes

[jcstein]

Overview

[gemini-code-assist]

Summary of Changes

Hello @jcstein, I'm Gemini Code Assist¹! 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 updates the hardware requirements documentation to reflect a revised CPU recommendation for bridge nodes. The change specifically increases the suggested core count from 8 to 32 for both non-archival and archival bridge node setups, aiming to provide more accurate and robust guidance for users setting up these nodes.

Highlights

• Bridge Node CPU Requirement Update: The recommended CPU core count for bridge nodes has been significantly increased from 8 cores to 32 cores in the hardware requirements documentation.
• Documentation Consistency: This update applies to both non-archival and archival bridge node configurations, ensuring the documentation provides consistent and up-to-date hardware specifications.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the hardware requirements documentation in app/operate/getting-started/hardware-requirements/page.mdx. Specifically, it increases the CPU requirement for Bridge nodes from 8 cores to 32 cores in both the non-archival and archival data availability node sections. A minor formatting adjustment was also made to the 'Disk' column header in the non-archival consensus nodes table. No review comments were provided.