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
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,11 @@ All recommendations here should be be used as a starting point. Further benchmar

For a simple deployment the following configuration works well:
* Network: Indexer, Conduit, Algod and PostgreSQL should all be on the same network.
* Indexer: 2 CPU and 8 GB of ram.
* Conduit: 2 CPU and 8 GB of ram.
* Indexer: 1 CPU and 1GB of ram. Scale up for systems with high query volume.
* Conduit + Algod: 4 CPU and 8 GB of ram.
* Storage: algod follower nodes, 40 GiB, 3000 IOPS minimum.
* Deployments allocating less ram might work in conjunction with [GOMEMLIMIT](https://pkg.go.dev/runtime@master#hdr-Environment_Variables) for Algod (and even Conduit). This configuration is not tested, so use with caution and monitor closely.
* Database: When hosted on AWS a `db.r5.xlarge` instance works well.
* Storage: 20 GiB

A database with replication can be used to scale read volume. Configure a single Conduit writer with multiple Indexer readers.

Expand Down