...
The following table lists the typical usage characteristics for each setup edition, and the physical or virtual resources it requires.
Available in Edition | Load Configuration Architecture | Goal | TPS Limit (4) | Supports Virtual Environment | Cores (1) | RAM (3) | Storage |
---|---|---|---|---|---|---|---|
Developer | Development | Developers only. In rare cases can be used for functional POCs. | 2-3 TPS | Can be virtual | 2 cores | 3 GB | Single disk: 25GB |
Standard | Minimal | POCs and Evaluation. | 5 TPS | Can be virtual | 4 cores | 18 GB | OS: 40 GB |
Standard | Low | Environment with low load levels | 40 TPS | Can be virtual | 6 cores | 32 GB | OS: 40 GB |
Standard | Medium | Environment with Moderate load | 80 TPS | Can be virtual | 8 cores | 64GB | OS: 40 GB |
Standard | High | Environment with Moderate load | 120 TPS | Can be virtual, but not recommended | 12 cores | 128GB | OS: 40 GB |
Standard | High_20dv | Environment with Medium load | 200 TPS Can be increased to 1500 TPS by adding resources(5) | Must be installed on a physical server | 16 cores | 200GB | OS: 40 GB |
Standard | High_20dv | Environment with High load | 1500 TPS(5) | Must be installed on a physical server | 24 cores(5) | 256GB | OS: 40 GB |
Standard | High_20dv | Environment with Very High load | 2750 TPS(6) | Must be installed on a physical server | TBD(6) | TBD(6) | TBD(6) |
Standard | Federated Architecture | Environment with Very High load | >2750 TPS - TBD(6) | Must be installed on physical servers | TBD(6) | TBD(6) | TBD(6) |
High Load capacity plan sizing example
...