-
Notifications
You must be signed in to change notification settings - Fork 93
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.
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
Update system requirements. #1581
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1581 +/- ##
=======================================
Coverage 68.58% 68.58%
=======================================
Files 37 37
Lines 7417 7417
=======================================
Hits 5087 5087
Misses 1903 1903
Partials 427 427 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
README.md
Outdated
* Database: When hosted on AWS a `db.r5.xlarge` instance works well. | ||
* Storage: 20 GiB | ||
* Storage: 20 GiB, 3000 IOPS minimum. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might put together Indexer, Conduit, and Storage into one requirement, like Indexer/Conduit: 4 CPU and 8 GB of RAM, 20 GB storage (3000 IOPS minimum)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we recommending to deploy all 3 together, or Conduit/Algod, then Indexer on it's own? I made some adjustments to the Conduit PR assuming Algod+Conduit, but should decide how that impacts this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For security, they might want to put Indexer on a separate machine -- its the only thing that needs to be exposed to clients. For performance, it can live alongside Conduit/Algod unless read volume is so high that it needs to be elsewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can get behind that approach Will
Co-authored-by: Gary <982483+gmalouf@users.noreply.github.com>
Summary
Update system requirements section of README.
Test Plan
N/A