docs icon indicating copy to clipboard operation
docs copied to clipboard

docs: Increase LN disk recommendation to 100GB and bridge/full RAM to 16GB

Open Wondertan opened this issue 1 year ago • 3 comments

It's supposed to be temporary to give us some buffer until the sample and header pruning is finished. Afterward, we can revert and even decrease to ~5GB with pruning milestones finished.

Summary by CodeRabbit

  • Documentation
    • Updated the minimum required SSD storage for a light node from 50 GB to 100 GB.
    • Updated the minimum recommended memory requirement for bridge and full-storage nodes to 16 GB RAM.

Wondertan avatar May 07 '24 13:05 Wondertan

[!IMPORTANT]

Auto Review Skipped

Review was skipped due to path filters

Files ignored due to path filters (1)
  • public/img/node-requirements.jpg is excluded by !**/*.jpg

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The recent updates involve increasing the minimum SSD storage requirement for light nodes to 100 GB and updating the minimum recommended memory requirement for bridge and full-storage nodes to 16 GB RAM. These changes aim to enhance the performance and stability of the nodes under varying resource constraints.

Changes

File Path Change Summary
nodes/light-node.md Updated SSD storage requirement from 50 GB to 100 GB
nodes/bridge-node.md Updated minimum recommended memory from 4 GB to 16 GB RAM
nodes/full-storage-node.md Updated minimum recommended memory from 4 GB to 16 GB RAM

🐇✨ In the land of code and node,
A rabbit hopped down the storage road.
"Make room, make room!" it cheerily cried,
"For bytes and bits need space to abide!"
Now with a hundred gigs to play,
Our nodes will hum a brighter day.
🌟📀

Possibly related issues

  • celestiaorg/celestia-app#2935: This update aligns with the objective of addressing crashing issues in consensus-full-nodes due to insufficient RAM. By increasing the minimum RAM requirement for nodes, stability is prioritized over sync speed, potentially mitigating the problem outlined in this issue.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • 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.

coderabbitai[bot] avatar May 07 '24 13:05 coderabbitai[bot]

PR Preview Action v1.4.7 :---: Preview removed because the pull request was closed. 2024-05-08 15:15 UTC

github-actions[bot] avatar May 07 '24 13:05 github-actions[bot]

TODO

  • [x] revise diagram to say 100GB
  • [x] revise diagram to say 16GB for RAM for bridge/full

jcstein avatar May 07 '24 14:05 jcstein