App Install
Measure app installation speed. This scenario has two roles:
minimal: Installs a simple app which implements initialisation callbacks but otherwise doesn't contain a lot of code.large: Installs a larger app that contains some dependencies and some generated data as padding to make the bundle larger.
These are intended to catch a compilation slowdown or issues with copying around large WASMs (e.g. accidental cloning or tracing). In each case, the behaviour will uninstall the app it installed so that it can re-install it on the next iteration.
-
minimal(1 agent)
App Install
Measure app installation speed. This scenario has two roles:
minimal: Installs a simple app which implements initialisation callbacks but otherwise doesn't contain a lot of code.large: Installs a larger app that contains some dependencies and some generated data as padding to make the bundle larger.
These are intended to catch a compilation slowdown or issues with copying around large WASMs (e.g. accidental cloning or tracing). In each case, the behaviour will uninstall the app it installed so that it can re-install it on the next iteration.
-
large(1 agent)
DHT Sync Lag
Measure lag time between an agent publishing data and other peers being able to see it. This scenario has two roles:
write: A simple job that just creates entries with a timestamp field. Those entries are linked to a known base hash. For each write, the metricws.custom.dht_sync_sent_countis incremented.record_lag: A job that repeatedly queries for links from the known base hash. It keeps track of records that it has seen and when a new record is found, and calculates the time difference between the timestamp of the new record and the current time. That time difference is then recorded as a custom metric calledwt.custom.dht_sync_lag.
After each behaviour loop the metric ws.custom.dht_sync_recv_count is incremented.
-
record_lag(5 agents) -
write(5 agents)
agent:uhCAk4_z1A9z_B2eVAAIHaLvS_Vl4pXI82Jhv3CPZ2XyS8it8OLRb
agent:uhCAkFBadkJafkU7J09SfE_lQSmJT9zuuUqm8nrux4vHzSlwe2l0a
agent:uhCAkN3or74MjFgpZyXplUM3CRCGBhkTJfuwnY6tn1E5EVoYy7NTP
agent:uhCAkQSdn4v2v1adtdafN4ze5LcyF95BOU2WNX4HLpfwDJE4t7F9s
agent:uhCAkhYDxjo87_73TOD-camL49mZm6EjOJdBCXECrauWgAWjvVVNL
agent:uhCAkEkNESHlDWIrYElPlx7i507_YZpxLnFK3tYHyeywlsSAYAUHH
agent:uhCAkHKCZnXkUriQqId8YbH15blltiODg5McPwXUoce9kCb4Tc76Q
agent:uhCAkNjS1LaCK3wc7Ykyjp83h1qm3cNkWhHMTrJD8IdDFTVXgwfzw
agent:uhCAkulfIkOwhNL67cfIk8V_aNvAN-ueJ7KjtQjFUB7MJk-QjjV5W
agent:uhCAkwZME3fzCY7xXhEmhIRlB-iQL79cA3GFkGFpYzZfzMF_-Y8uT
agent:uhCAkEkNESHlDWIrYElPlx7i507_YZpxLnFK3tYHyeywlsSAYAUHH
agent:uhCAkHKCZnXkUriQqId8YbH15blltiODg5McPwXUoce9kCb4Tc76Q
agent:uhCAkNjS1LaCK3wc7Ykyjp83h1qm3cNkWhHMTrJD8IdDFTVXgwfzw
agent:uhCAkulfIkOwhNL67cfIk8V_aNvAN-ueJ7KjtQjFUB7MJk-QjjV5W
agent:uhCAkwZME3fzCY7xXhEmhIRlB-iQL79cA3GFkGFpYzZfzMF_-Y8uT
First Call
This scenario installs a simple app which implements the init callback, and measures the time elapsed between start of install and calling init. It will uninstall the app it installed so that it can re-install it on the next iteration. This is required to re-run the initialisation callback.
- Default (1 agent)
init.Local Signals
This scenario is for testing the speed and reliability of local signals. It uses a zome with a function that will emit 10,000 signals. The scenario measures how long it takes to send the signals and how many have been received by the time the zome call ends.
- Default (1 agent)
No scenario template for mixed_arc_get_agent_activity!
No scenario template for mixed_arc_must_get_agent_activity!
Remote Call Rate
Test the throughput of remote_call operations. Each agent in this scenario waits for a certain number of peers to be available or for up to two minutes, whichever happens first, before starting its behaviour.
- Default (1 agent)
agent:uhCAk1uzI7UABmtp_-M9xS7tD6ufDXDX7PlIBCjJoY7zM0eDEIFcj
agent:uhCAkNiKY8mkteqIMGUr2tki5BpRqryoSYPwOwgUVQkSlvVwJ2TrG
agent:uhCAk1uzI7UABmtp_-M9xS7tD6ufDXDX7PlIBCjJoY7zM0eDEIFcj
agent:uhCAkNiKY8mkteqIMGUr2tki5BpRqryoSYPwOwgUVQkSlvVwJ2TrG
Remote Signals
This scenario tests the throughput of remote_signals operations.
- Default (1 agent)
Single-write, many-read
Creates an entry in the agent setup, then read one's own record back. This tests the maximum read performance for reading back local data when the chain is short.
- Default (1 agent)
read call timingread call rate (10s)Validation Receipts
Creates an entry, wait for required validation receipts, then repeat. Records the amount of time it took to accumulate the required number of receipts for all DHT operations. This is measured to the nearest 20ms so that we don't keep the agent too busy checking for receipts.
Each agent in this scenario waits for a certain number of peers to be available or for up to two minutes, whichever happens first, before starting its behaviour.
By default, this scenario will wait for a complete set of validation receipts before committing the next record. If the NO_VALIDATION_COMPLETE environment variable is set, it will instead publish new records on every round, building up an ever-growing list of action hashes to check on.
- Default (1 agent)
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:RegisterAgentActivity
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:StoreEntry
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:StoreRecord
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:RegisterAgentActivity
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:StoreEntry
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:StoreRecord
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:RegisterAgentActivity
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:StoreEntry
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:StoreRecord
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:RegisterAgentActivity
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:StoreEntry
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:StoreRecord
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:RegisterAgentActivity
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:StoreEntry
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:StoreRecord
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:RegisterAgentActivity
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:StoreEntry
agent:uhCAk7SS9PePFHDXb2D38PzZQ4fMkNC21CdJ81GCejRaJypJ6k0Jcop_type:StoreRecord
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:RegisterAgentActivity
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:StoreEntry
agent:uhCAkEXguGjkyf1QVFvyG6-97Ix62pY6Piu94mnuS4gZmBGYfHTftop_type:StoreRecord
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:RegisterAgentActivity
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:StoreEntry
agent:uhCAkFRnAHvb1uzXUCLox2sw0S2K0TWlufuIjiS0NrEw9Cxc2YiiRop_type:StoreRecord
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:RegisterAgentActivity
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:StoreEntry
agent:uhCAkfdcuWQG3Ifn9AVtxfoALDEG6lx7zEmXs5E_2QiuQphsCGWNfop_type:StoreRecord
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:RegisterAgentActivity
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:StoreEntry
agent:uhCAktgyeZaGfPy8eA87lHZtNreLoQfwHqByTV4z1W94NApZ8l3HBop_type:StoreRecord
Write/get_agent_activity
A scenario where write peers write entries, while get_agent_activity peers each query a single write agent's activity with get_agent_activity.
Before a target write peer and the requesting get_agent_activity peer are in sync, this will measure the get_agent_activity call performance over a network. Once a write peer reaches sync with a get_agent_activity peer, the write peer will publish their actions and entries, and so the get_agent_activity calls will likely have most of the data they need locally. At that point this measures the database query performance and code paths through host functions.
-
get_agent_activity(1 agent) -
write(1 agent)
action_seqwrite peer's source chain.get_agent_activity_full zome call timingwrite peer's source chain.agent:uhCAkvVXtnu-K-Q19tl4fFlg24bndUfnO7-PodOGzfIDX17fvbEIo
Write/Query
Creates an entry, then queries the source chain and performs a simple operation on the entries, then repeats.
- Default (1 agent)
Write/Read
Creates an entry and reads it back, then repeats.
- Default (1 agent)
Write validated
Creates an entry, updates it and links the create to the update, then repeats. Each of the three actions is validated by the included hApp.
- Default (1 agent)
Write Validated must_get_agent_activity
A scenario where write agents create entries, while must_get_agent_activity agents create entries which are validated with a must_get_agent_activity call for a single write agent's activity.
Before a target write peer and the requesting peer are in sync, the must_get_agent_activity request will go over the network. Once a write peer reaches sync with the requesting must_get_agent_activity peer, the write peer will publish their actions and entries, and so the must_get_agent_activity calls will likely have the data it needs locally. At that point this measures the database query performance and code paths through host functions.
-
must_get_agent_activity(1 agent) -
write(1 agent)
action_seqmust_get_agent_activity peer's source chain top over the run.create_validated_sample_entry zome call timingwrite agent's source chain.agent:uhCAkKwwiZ3HT1hqp_ImHFMhyZfW5p9mKeUPmvJU3CE55zIkh8--r
Zero-Arc Create and Read
A zero-arc/full-arc mixed scenario with two types of zero-arc nodes -- ones that create data and ones that read data -- as well as full arc nodes to "relay" the data. The scenario has three roles:
zero_write: A zero-arc conductor that just creates entries with a timestamp field. Those entries are linked to a known base hash so thatzero_readnodes can retrieve them.zero_read: A zero-arc conductor that reads the entries created by the zero-arc node(s) and records the time lag between when the entry had been created and when it was first discovered.full: A full-arc conductor that is just here to serve entries to zero arc nodes.
-
full(3 agents) -
zero_read(3 agents) -
zero_write(3 agents)
agent:uhCAk5OykQR65Bjx1_qXUP6hW4NozOF8hY_SODBOmih2QzeRO_vLi
agent:uhCAkFH7TqdylU825nEKxd7TP4IJ4BJjtYPPMDfluUirhKfAblQgL
agent:uhCAkno8a_YZYIMr-33hJf0GeAGJk-Ji-jr3nLMAe5ysCrfP8RR4n
get_timed_local_entries zome function.agent:uhCAk2B1-1eu6sUuNHiNOpYK-Cw_3elH0JQfwOnsf6YXyH54wDwYf
agent:uhCAk8vhndSy4j5CG9seYcR24xlsDzbCV5qRMjLq4OdDdTDzLy5JM
agent:uhCAkE23V0Z4FaflnvgkqSMXx8EQbWQd2NcGH5NWvDdVDu4KRSs1m
agent:uhCAk2B1-1eu6sUuNHiNOpYK-Cw_3elH0JQfwOnsf6YXyH54wDwYf
agent:uhCAk8vhndSy4j5CG9seYcR24xlsDzbCV5qRMjLq4OdDdTDzLy5JM
agent:uhCAkE23V0Z4FaflnvgkqSMXx8EQbWQd2NcGH5NWvDdVDu4KRSs1m
Zero-Arc Create Data
zero: A zero-arc conductor that just creates entries with a timestamp field. Those entries are linked to a known base hash so that full-arc nodes can retrieve them.full: A full-arc conductor that reads the entries created by the zero-arc node(s) and records the time lag between when the entry had been created and when it was first discovered.
-
full(4 agents) -
zero(6 agents)
agent:uhCAk39cMMHcJ3RZw8LRZuTC8jgmgLe39zcl26ldEdMhvKfLaZkeQ
agent:uhCAkBSTkNeoanebaDA5glciP9uXjUXhgwBq7xhXBzF5N7pr-olOI
agent:uhCAkCGKlTF9wClsknyiqcWJ_SI5RS_mkf8zGzK7D0Fmd0DYuTAe1
agent:uhCAkSINaDDZo9yGoLwvFqWUqZP-ezQhbuU9C9mvghu_uEmGz_fdF
agent:uhCAkbKoYInJ6Sv4gzzoGbLXsYiYaQ3iCcLZgaQHtqIxnghZTpR9i
agent:uhCAkxXhTu2fzh_OrxzyBH9FvrU-YOhq2jk2GkYR4RZaWZo8uDb7r
get_timed_local_entries zome function.agent:uhCAk2j97S6W72_zqCfgTlMjhcE6nN65TOwsNZeCkHVGu5TM8PZBG
agent:uhCAkAdh7fJOJJ7dgr70FBZdwRMSjh1AXb9HvU5AH-aQRpsdNYALX
agent:uhCAkBy8gDu8CK-UQ3O-hFFTdH_4J_AvGfVeSHc02kcBe03MZTVO4
agent:uhCAkess7fmmE-2i-dyhD-wi5SVbNyadgnCEddBXPz0qFvIvP8rqz
agent:uhCAk2j97S6W72_zqCfgTlMjhcE6nN65TOwsNZeCkHVGu5TM8PZBG
agent:uhCAkAdh7fJOJJ7dgr70FBZdwRMSjh1AXb9HvU5AH-aQRpsdNYALX
agent:uhCAkBy8gDu8CK-UQ3O-hFFTdH_4J_AvGfVeSHc02kcBe03MZTVO4
agent:uhCAkess7fmmE-2i-dyhD-wi5SVbNyadgnCEddBXPz0qFvIvP8rqz
Zero-arc Create Data (Validated)
A zero-arc/full-arc mixed scenario where zero-arc nodes create data that gets validated and full-arc nodes read the data. The scenario has two roles:
zero: A zero-arc conductor that just creates entries with a timestamp field. Those entries are linked to a known base hash so that full-arc nodes can retrieve them.full: A full-arc conductor that reads the entries created by the zero-arc node(s) and records the time lag between when the entry had been created and when it was first discovered.
-
full(4 agents) -
zero(6 agents)
agent:uhCAkBUt036PQc3sTfiuEdOsKWorH6BHK9WlhkbI2QmVpjdcEKQAb
agent:uhCAkJPpaNlRyBZOvniE4NN0tpyAGU-_AbZkT_Ne-FIKa0NkoM0ra
agent:uhCAkR1sV3c0uAEYRJ4MtrGoA7_fQw-mkUZWbXP8KhKk2tW5npVVj
agent:uhCAkVHUBveiS-NVLGJBIQZrsJHz-EIixr4aAFFRtal6zUbn9fCB-
agent:uhCAkYvUL6VPO2RzE8dH0-DjusSjLYCw7MekMGMqsdIa9dQU94z7u
agent:uhCAkqWgKf2HqhjVN3hjO8JCo4GpE49bCbTJWWHmJP1BK6A_aFvrD
get_timed_local_entries zome function.agent:uhCAk5C3ntx4KN4uBsHDMn13fdKDkg6p46TIPWfzXkqhfdi4gQKCa
agent:uhCAkC62WwM5MVV4hh-DH-24GqwiliXldbdi8KiZhAnlnhHLRxU8N
agent:uhCAktfPR7yvqYNYrZZoYPqcQr858A6x69GwV5sM6m8vyavf3W2DY
agent:uhCAkx1TNWquRs5gbccG9NpYzvDUDplXenzbohkmRdXhdb3mquXwk
agent:uhCAk5C3ntx4KN4uBsHDMn13fdKDkg6p46TIPWfzXkqhfdi4gQKCa
agent:uhCAkC62WwM5MVV4hh-DH-24GqwiliXldbdi8KiZhAnlnhHLRxU8N
agent:uhCAktfPR7yvqYNYrZZoYPqcQr858A6x69GwV5sM6m8vyavf3W2DY
agent:uhCAkx1TNWquRs5gbccG9NpYzvDUDplXenzbohkmRdXhdb3mquXwk
Zome Call, Single Value
Calls a zome function that returns a fixed value. This tests the maximum performance of zome calls when the zome function is not calling into Holochain other otherwise doing any work.
- Default (1 agent)