Skip to content

fix: update Large hardware tier description to reflect current network scale#1091

Open
cargopete wants to merge 1 commit intographprotocol:mainfrom
cargopete:fix/hardware-requirements-clean
Open

fix: update Large hardware tier description to reflect current network scale#1091
cargopete wants to merge 1 commit intographprotocol:mainfrom
cargopete:fix/hardware-requirements-clean

Conversation

@cargopete
Copy link
Copy Markdown
Contributor

Summary

The Large setup description states it is "Prepared to index all currently used Subgraphs" — this is no longer accurate and is misleading to indexers planning their infrastructure.

The problem:

  • These figures were written when the network had far fewer subgraphs
  • The network now has 15,000+ Subgraphs (as of 2026)
  • Community operators report ~600 GB total RAM for ~1,700 Subgraphs (data from Marc-André / Ellipfra, April 2026)
  • The Large tier (468 GB Postgres + 184 GB VMs = ~652 GB total) covers roughly 1,500–2,000 Subgraphs, not the full network

The fix:
Updated the Large tier description to accurately reflect ~1,500–2,000 Subgraph capacity and note that full-network indexing requires substantially more resources.

Supporting data

The table values (CPUs, disk) are left unchanged — only the description was inaccurate.

@cargopete cargopete requested a review from a team as a code owner April 7, 2026 15:32
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.

1 participant