Hyperledger Fabric sizing might be a little tricky. One way of doing is to design the number of Fabric specific components, like CA (Certificate Authorities), Peers and Ordering Services components, getting some baselines for the designed system and accumulating the result.
Simple development or test systems, might contain one peer, one ordering services, one certificate authorities and one channel. Complex productive systems usually have several organizations containing at least two but rather three peers for each organization, several certificate authorities like one for each organization and a complex ordering services usually containing at least five ordering containers.
Baselines for the container resources can be gained from different resources, like this one. The following tables contains possible sizing for each container as virtual resource.
Dev / Demo system:
- CA: 0.1 vCPU / 0.2 GB RAM / 20 GB Disk
- PEER: 1.1 vCPU / 2.8 GB RAM / 100 GB Disk
- ORDERING: 0.35 vCPU / 0.7 GB RAM / 100 GB Disk
Test / Pilot system:
- CA: 0.1 vCPU / 0.2 GB RAM / 20 GB Disk
- PEER: 2 vCPU / 4 GB RAM / 200 GB Disk
- ORDERING: 1 vCPU / 1 GB RAM / 200 GB Disk
Productive system:
- CA: 0.1 vCPU / 0.2 GB RAM / 20 GB Disk
- PEER: 4 vCPU / 8 GB RAM / 500+ GB Disk
- ORDERING: 1 vCPU / 1 GB RAM / 500+ GB Disk
Certainly the above number can be modified based on the used containerization and virtualization technology.
