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)
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)
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:uhCAk-3t5h8WPARm_OWkai3oFnItcSc7rlEUi4VnkqRU7phtwFRUO
agent:uhCAk3tvkprl2t0ChJJOMqB-e7RYjidBti4qEiDz2ByNf40nQviF2
agent:uhCAkT46cr2hNvY2-PCpIOC6Z7-DTKnfo9fldmzyDcZBNquMgkmqM
agent:uhCAkn8S7aHadpVfOI3F_gZBRLWTFe-8kp8cXJoEEGmQFStdS5exj
agent:uhCAksBsN4TOvK_Lc5mX9xkqDsAw09S6fhS5mPJzOjPQQR5R-XXUW
agent:uhCAkQQnW7E92iC5cVKAN3jMS4kJZW9Nn7pIAHCy2VIjQsQNztZZB
agent:uhCAkQuy-B0Yr65bGGc1lL0xcaFgjeKMiq7fNQ8XafEkmYf2RUVPP
agent:uhCAkWT39kueOgDbXRyPfEibZJeH1pAyazPFMl_VXHkhj-Y1Ew_eq
agent:uhCAkYKwxBo3kxEAQLhiRK1LQb2IG5uyCtAdFLNMMewJ3M91_RDMR
agent:uhCAkpHQEuW8sjQfvw3g6kIR3RZVYlHCeaCxnP2I5oA8GMpYePzFm
agent:uhCAkQQnW7E92iC5cVKAN3jMS4kJZW9Nn7pIAHCy2VIjQsQNztZZB
agent:uhCAkQuy-B0Yr65bGGc1lL0xcaFgjeKMiq7fNQ8XafEkmYf2RUVPP
agent:uhCAkWT39kueOgDbXRyPfEibZJeH1pAyazPFMl_VXHkhj-Y1Ew_eq
agent:uhCAkYKwxBo3kxEAQLhiRK1LQb2IG5uyCtAdFLNMMewJ3M91_RDMR
agent:uhCAkpHQEuW8sjQfvw3g6kIR3RZVYlHCeaCxnP2I5oA8GMpYePzFm
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.No scenario template for full_arc_create_validated_zero_arc_read!
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_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:uhCAkO0eTK_7gk-QljJ7b7y98iVsqf5tfWVnb831L1N1EP9ct-D9Y
agent:uhCAkYySRL2J9sNRQLX1cg5u01pTtwiRnRHiTSrgb4Ye_J09AjMNm
agent:uhCAkO0eTK_7gk-QljJ7b7y98iVsqf5tfWVnb831L1N1EP9ct-D9Y
agent:uhCAkYySRL2J9sNRQLX1cg5u01pTtwiRnRHiTSrgb4Ye_J09AjMNm
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)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:uhCAkEc_5lZIoE_a_pyMv3xWVQBZxjawwNmyoIzMYI3nyt67fO8ry
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:uhCAkas9x08dV_iE4ELwaCoQbA5JiF2OqUmBoC0Jd5HxKMevGC9Eq
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:uhCAk7v0Bu-NSK_jNWJ_4T3NPrTDNHVEBguU_E7v14lqtOz3k-RBl
agent:uhCAkqiNZXsYDFj4beq7I5n_lVYwdna6NChLa1fyzlMbEpIbNW1Nc
agent:uhCAkwxjp1Mf_xdep2p_Is4IGSgn3NAxe_Ia0uw3kB7t-F7uUxrTa
get_timed_local_entries zome function.agent:uhCAk1j034uQo_zLLOcA99pROYJAYQa09DVb1C7isX4RWnlX6cr32
agent:uhCAkLjGXd9MLcsxqeq48o-tOVMDHyj-gd2Vpym5ivnaIi94gOPkJ
agent:uhCAkwCiomRneFJr0oY5qbbnpwUROjsex0rjVZV-i1_ivrIUSSiNv
agent:uhCAk1j034uQo_zLLOcA99pROYJAYQa09DVb1C7isX4RWnlX6cr32
agent:uhCAkLjGXd9MLcsxqeq48o-tOVMDHyj-gd2Vpym5ivnaIi94gOPkJ
agent:uhCAkwCiomRneFJr0oY5qbbnpwUROjsex0rjVZV-i1_ivrIUSSiNv
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:uhCAk-VPRd8ToiK-KXu0uPBKSL9wkLAdTCylrPBcXWFsZOcJtIW0e
agent:uhCAkChklv83QV-KXXbA2oU_2zJvBtCTlUa2EJ1md_KN7bbAg5CWl
agent:uhCAkJcP6FW1Y_F8XfCPXT2Bb2X5jujkvH3fl-SF1neLdXUhxvZ2h
agent:uhCAkQsjyb8qzT3LojCtfkHYjZO0RotR67rXUmb5axr1-KngE_2Lh
agent:uhCAkUHRQTaAfyZ4jQUhxbEZkyc14j22SFeQGIN874365NjzBatxy
agent:uhCAkwT7RzKI7wSi4lTGyVEpG7adFIYWUZTM507siaKovGYkHJgSC
get_timed_local_entries zome function.agent:uhCAkMUuXK8eBfRU4C98JyXcbSoZOSYkTpLDs1L2VUOUqPuuy8_zI
agent:uhCAkUb6mKVPCEV553xjZBq6dG5O6y0mP7Nmp7OymheXqZsaFOJ0b
agent:uhCAkjOv2tJHX1VBVGLh-hB-04hW5ItCUtvMXs5x1hcBlGizUP7rw
agent:uhCAkluzBKgkHLefLx1MZLf0ttjaNXJqNgnTys9KAvNJmgCzZ6-3y
agent:uhCAkMUuXK8eBfRU4C98JyXcbSoZOSYkTpLDs1L2VUOUqPuuy8_zI
agent:uhCAkUb6mKVPCEV553xjZBq6dG5O6y0mP7Nmp7OymheXqZsaFOJ0b
agent:uhCAkjOv2tJHX1VBVGLh-hB-04hW5ItCUtvMXs5x1hcBlGizUP7rw
agent:uhCAkluzBKgkHLefLx1MZLf0ttjaNXJqNgnTys9KAvNJmgCzZ6-3y
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:uhCAk-9QzLe1xvfH-m8a5RhtUBnn5Atq1NnAGj4ZGfawwxtktmzO5
agent:uhCAk94s3Cr-UKl5oINlrJw0St5BEfp1hngm_GyoYw1Ly51Q9oZrv
agent:uhCAkcvJut_lp5UGcRFUPtzqcAxl1-8uGa-W7ACdNTAb0SYvWydP6
agent:uhCAkp9wSOjiHy1AP9P2XdWoAxFArUJHgfZkEj7Q0hLI_QMBwUhTB
agent:uhCAkq3RpbHII8jZrdl2_90Y3EGvJgeal1dIRKr-0qswql3n3Am_5
agent:uhCAksG6ZJEkmxIcNdE8g9HFZYneCsFAE3hlXYT_ljO5HcH6Yp-VB
get_timed_local_entries zome function.agent:uhCAk6dYVWy9gsc6GLkz9cR-MWkpZnXNtlznEm213OKuE5LN281c3
agent:uhCAkOerWZb8z-8y6NWStbbFyZN8jA3hDYCZWlPAr-dC6zNi3IPqS
agent:uhCAkj2wBHRWlSt3YBx56K3dGKw9bFAgPhpeH-TOYv4XosTFNd5Ra
agent:uhCAklRaOXpP4_RvecNlUjzWSG8HJY2id5DFzu00k9hexqsPoWR_L
agent:uhCAk6dYVWy9gsc6GLkz9cR-MWkpZnXNtlznEm213OKuE5LN281c3
agent:uhCAkOerWZb8z-8y6NWStbbFyZN8jA3hDYCZWlPAr-dC6zNi3IPqS
agent:uhCAkj2wBHRWlSt3YBx56K3dGKw9bFAgPhpeH-TOYv4XosTFNd5Ra
agent:uhCAklRaOXpP4_RvecNlUjzWSG8HJY2id5DFzu00k9hexqsPoWR_L
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)