Blockchain Infrastructure Calculator
How Much Hardware Does Hyperledger Fabric Need?
Free calculator to estimate CPU, RAM, and storage requirements for your Hyperledger Fabric network. Size your infrastructure based on organizations, peers, orderers, consensus type, and target TPS.
Blockchain Resource Sizing Calculator
Calculate infrastructure requirements for production and testnet environments based on your network configuration
Independent entities participating in the network
Total peers: 4 (2 orgs × 2 peers)
Raft: Minimum 5 orderers for production (tolerates 2 crash failures)
Your Network Configuration
Production requirements • Testnet uses ~50% less resources
Your Hyperledger Fabric Hardware Requirements Summary
For a 2-organization, 4-peer Hyperledger Fabric network with 5 RAFT orderers targeting 100 TPS: Production requires 29.6 vCPUs, 61 GB RAM, and 57.1 TB storage. Each peer node needs 4.4 vCPUs and 9 GB RAM, while orderer nodes require 2.4 vCPUs and 5 GB RAM. Raft consensus provides efficient crash fault tolerance with lower resource overhead. This mid-range TPS configuration is typical for enterprise blockchain deployments.
How It Works
Understanding Resource Requirements
Learn how we calculate infrastructure needs for blockchain networks.
Network Components
- •Peer Nodes: Maintain the ledger, execute chaincode, and validate transactions
- •Orderer Nodes: Order transactions into blocks and ensure consensus
- •Organizations: Independent entities with their own peers and certificates
Scaling Factors
- •TPS Impact: Higher transactions per second require more CPU and faster storage
- •Consensus Overhead: BFT protocols require more resources than Raft
- •Network Size: More organizations increase cross-org communication needs
CPU Requirements
CPU scales with transaction validation, chaincode execution, and cryptographic operations. High TPS workloads need more cores.
Memory Requirements
RAM is used for state database caching, transaction pools, and chaincode containers. More memory improves query performance.
Storage Requirements
Disk size depends on ledger growth rate. IOPS requirements scale with TPS - use SSDs for production workloads.
Consensus Type Comparison
Raft (CFT)
Crash Fault Tolerant. Lower overhead, higher throughput. Recommended for trusted networks where nodes are not expected to act maliciously.
BFT / PBFT
Byzantine Fault Tolerant. Higher resource overhead but protects against malicious nodes. Required for networks with untrusted participants.
Hyperledger Fabric RAM Requirements
Fabric Peer Node Memory Requirements
A production Hyperledger Fabric peer typically needs 16-64GB RAM depending on workload. For low TPS (<100), 16GB is sufficient. Medium workloads (100-500 TPS) need 32GB. High-throughput networks (500+ TPS) benefit from 64GB+ for state database caching and chaincode execution.
Orderer Node Hardware Specifications
Orderer nodes are less resource-intensive than peers. For Raft consensus, 4-8 vCPUs and 8-16GB RAM handle most workloads. BFT consensus requires more resources due to additional message validation—typically 8-16 vCPUs and 16-32GB RAM.
Blockchain Storage Requirements
Fabric Ledger Storage Growth Rate
Ledger growth depends on transaction size and TPS. A typical transaction is 1-5KB. At 100 TPS with 2KB transactions, expect ~17GB/day or ~500GB/month of ledger growth. Plan for 1-10TB per peer for production networks with multi-year retention.
Blockchain SSD vs HDD IOPS Requirements
Always use SSDs (preferably NVMe) for production blockchain nodes. Ledger writes and state database queries require high IOPS. HDDs create bottlenecks above 50 TPS. For high-throughput networks, provision 10,000+ IOPS with NVMe drives.
Production vs Development Environment Sizing
Blockchain PoC Hardware Requirements
For development and testing: 4 vCPU, 8GB RAM, 100GB SSD per node. This supports single-organization networks with basic chaincode. Production pilots should use 8 vCPU, 16GB RAM minimum to accurately simulate performance characteristics.
Hyperledger Fabric 1000 TPS Requirements
High-throughput Fabric networks targeting 1000+ TPS need substantial resources: 32-48 vCPUs, 64-128GB RAM per peer, NVMe storage with 20,000+ IOPS, and 10Gbps network connectivity. Consider horizontal scaling with multiple endorsing peers per organization for optimal transaction throughput.
Raft vs BFT Resource Requirements
Blockchain Consensus Overhead Comparison
Raft (CFT) consensus is lighter—orderers need 4-8 vCPUs and 8-16GB RAM. BFT/PBFT adds ~30% overhead due to additional message rounds, requiring 8-16 vCPUs and 16-32GB RAM. Choose Raft for trusted networks; BFT for environments with untrusted participants where Byzantine fault tolerance is required.
Multi-Org Fabric Network Sizing
Each additional organization adds ~10% resource overhead due to cross-org communication and endorsement policies. A 4-org network with 2 peers each needs roughly 40% more total resources than a single-org network with 8 peers due to gossip protocol and transaction routing overhead.
Calculator Methodology
Baseline Requirements
- • Peer base: 4 vCPU, 8GB RAM, 100GB storage
- • Orderer base: 2 vCPU, 4GB RAM, 50GB storage
- • TPS multiplier: +50% resources per 100 TPS
- • BFT overhead: +30% CPU and memory vs Raft
Scaling Factors
- • Organizations: +10% resources per additional org
- • Peers per org: Linear scaling for endorsement
- • State DB: CouchDB adds +25% memory vs LevelDB
- • Safety margin: 20% headroom for production
These estimates are based on Hyperledger Fabric 2.x benchmarks and real-world deployments. Actual requirements may vary based on chaincode complexity, query patterns, and network topology. ChainLaunch can help you right-size your infrastructure based on your specific workload.