Skip to content
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

Merged
merged 5 commits into from
Oct 12, 2023
Merged

Update system requirements. #1581

merged 5 commits into from
Oct 12, 2023

Conversation

winder
Copy link
Contributor

@winder winder commented Oct 11, 2023

Summary

Update system requirements section of README.

Test Plan

N/A

@winder winder self-assigned this Oct 11, 2023
@codecov
Copy link

codecov bot commented Oct 11, 2023

Codecov Report

Merging #1581 (b1eefed) into main (e498ab7) will not change coverage.
The diff coverage is n/a.

@@           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.
Copy link
Contributor

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)

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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

README.md Outdated Show resolved Hide resolved
@winder winder merged commit 2517879 into algorand:main Oct 12, 2023
4 checks passed
@winder winder deleted the will/system branch October 12, 2023 15:08
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.

3 participants