Versions Compared

Old Version 4

changes.mady.by.user Vadim Reutskiy

Saved on

compared with

New Version 5

changes.mady.by.user Vadim Reutskiy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose: I that section you can find information about executed performance test runs for Iroha, all parameters and results.

...

Transaction configuration

  • Ordered batch 1
    • CreateDomain
    • CreateAsset
    • CreateAccount
    • AddAssetQuantity
    • TransferAsset
  • Ordered batch 2
    • GrantPermission
    • SetAccountDetail
  • Ordered batch 3
    • SetAccountDetail

Test types

  1. Soak testing: running Iroha network with 80% of peak load over a long time period (more than 24 hours) – to emulate behaviour under normal load on an extended period of time
  2. 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"

Metrics

During performance testing, our goal is to understand non-functional characteristics of running Iroha network in terms of speed and efficiency.

For a clear understanding of such characteristics, we are going to collect the following metrics:

...

:

  • Step 1. Obtaining information about peak load that Iroha network can handle:
    • Define the highest amount of transactions for a peak load of Iroha network during one hour (on the peak load the network should work stable, without significant deterioration of other characteristics: TPS, memory consumption, transaction finalization time, etc.). 
  • Step 2. Collecting data about Iroha characteristics (for each test type)
    • The maximum amount of successfully finalized transactions per second (TPS
    )
    • During 80% of peak load on a long-distance (more than 24 hours)
    • During 100% peak load on a short distance (1 hour)
    • Average time of transaction finalization (from the moment when the transaction reached the Torii port, until the moment when the transaction is marked as finalized and sent to the subscribers via opened streams)
    • When Iroha network is on the 80% of peak load
    • When Iroha network is on the 100% of peak load
    • Average memory consumption by Iroha nodes (first 10% of time interval should be omitted to minimize the influence of "heating up" stage)
    • When Iroha network is on the 80% of peak load
    • When Iroha network is on the 100% of peak load
    • Average memory consumption by Postgres storage (first 10% of time interval should be omitted to minimize the influence of "heating up" stage)
    • When Iroha network is on the 80% of peak load
    • When Iroha network is on the 100% of peak loadAverage CPU utilization by each node (first 10% of time interval should be omitted to minimize the influence of "heating up" stage)