Purpose: I that section you can find information about executed performance test runs for Iroha, all parameters and results.
...
| Iroha nodes | Virtual machines | Iroha memory | Postgres memory | Storage, per node |
|---|
| Configuration A | 50 | 10 (5 nodes per machine) | 5 Gb | 1 Gb | SSD, 100Gb |
| Configuration B | 6 | 3 (2 nodes per machine) | 5 Gb | 1 Gb | SSD, 100Gb |
Iroha configurations
| Max proposal size | Max rounds delay | MST enabled | MST expiration time | Proposal delay | Stale stream max rounds | Vote delay | Block store allocation |
|---|
| Iroha config A | 50 | 1000 |
500?????| file system |
| Iroha config B | 1000 | 500 | true | 1440 | 1000 | 100000 | 1000 | file system |
Transaction configuration
- Ordered batch 1 – create an account, add tokens and transfer them
- CreateDomain
- CreateAsset
- CreateAccount
- AddAssetQuantity
- TransferAsset
- Ordered batch 2 – grant permissions to set account details and set some data
- GrantPermission
- SetAccountDetail
- Ordered batch 3 – set account details
- Ordered batch 4 – create MST account, add signatory and mint some tokens
- CreateAccount
- SetAccountQuorum
- AddSignatory
- AddAssetQuantity
- Ordered batch 5 - send MST transfer (from an account created by ordered batch 4)
- Ordered batch 6 - get pending transactions (created by ordered batch 4) and confirm them
- Soak testing: running Iroha network with 80% of peak load over a long time period of time (more than 24 hours) – to emulate behaviour under normal load on an extended period of time
- Spike testing: running Iroha network with 100% of peak load over a shorter time period (around 1 hour) – to emulate behaviour at peaks of request during "rush hours"
...