From 64cd91a39e523d71bd4c1561015e846f0547194d Mon Sep 17 00:00:00 2001 From: neriumpete Date: Tue, 7 Apr 2026 18:32:12 +0300 Subject: [PATCH] fix: update Large tier hardware description to reflect current network scale --- website/src/pages/en/indexing/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/src/pages/en/indexing/overview.mdx b/website/src/pages/en/indexing/overview.mdx index 7027eb955f59..63dd0bd8b880 100644 --- a/website/src/pages/en/indexing/overview.mdx +++ b/website/src/pages/en/indexing/overview.mdx @@ -126,7 +126,7 @@ Indexers may differentiate themselves by applying advanced techniques for making - **Small** - Enough to get started indexing several Subgraphs, will likely need to be expanded. - **Standard** - Default setup, this is what is used in the example k8s/terraform deployment manifests. - **Medium** - Production Indexer supporting 100 Subgraphs and 200-500 requests per second. -- **Large** - Prepared to index all currently used Subgraphs and serve requests for the related traffic. +- **Large** - Sufficient for approximately 1,500–2,000 Subgraphs. Note: these figures predate significant network growth. As of 2026, the network has over 15,000 Subgraphs; community operators report ~600 GB total RAM for ~1,700 Subgraphs. Indexing the full network requires substantially more resources than this tier provides. | Setup | Postgres
(CPUs) | Postgres
(memory in GBs) | Postgres
(disk in TBs) | VMs
(CPUs) | VMs
(memory in GBs) | | --- | :-: | :-: | :-: | :-: | :-: |