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:uhCAk2k_czQH99hFj_T040Pxg1IMahR1--qUTiTzEOYsanFjCiua7
agent:uhCAk9KM5xHJo9kCQkN0Web3rH2nhvXjrfYLZET1IggW1D0C3v8Rf
agent:uhCAkIf8uRrHvzoOySBO0eq1YDGQWqXUcRSGb7HTgTsAfM6iHVKfz
agent:uhCAkV-gMuLTmb4H-6sYEaoR364gRzogVY7HMNul73nAkyj3QZacQ
agent:uhCAkdR7Y4E3Xvxh96PZy1vMNB6TwLzdIrLHM-oFkYTHPjOa75wDg
agent:uhCAk77WYmORRd6PQC-8E3iE3CGsob2yl8qf0gV8cr09JMoW1wzIG
agent:uhCAkHdO422Of5OOkOQOgAMaHMdmGzL7FmAl_lfpxCmHMgIivil-W
agent:uhCAkHvYksGU_sp3giu7S62wsh4g7oTpWzdEzWOPIH4MYpLN-eqk9
agent:uhCAkcZtsRJwWKy1Mvu2Esp7LWMMbaDDy0DM80En6Cv5DKXsVxO_n
agent:uhCAkmoQU_emgr0dxRVIi9Omm98dbfs1bvQrzEuBuzvZczZPR3C9M
agent:uhCAk77WYmORRd6PQC-8E3iE3CGsob2yl8qf0gV8cr09JMoW1wzIG
agent:uhCAkHdO422Of5OOkOQOgAMaHMdmGzL7FmAl_lfpxCmHMgIivil-W
agent:uhCAkHvYksGU_sp3giu7S62wsh4g7oTpWzdEzWOPIH4MYpLN-eqk9
agent:uhCAkcZtsRJwWKy1Mvu2Esp7LWMMbaDDy0DM80En6Cv5DKXsVxO_n
agent:uhCAkmoQU_emgr0dxRVIi9Omm98dbfs1bvQrzEuBuzvZczZPR3C9M
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_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:uhCAk-OELMm-yJ2Kx2jF9IMh07dnG_MQfJvdFPNkT5YusX-a-dQVX
agent:uhCAkvKOu6TN3Ar6mGW84WPEBOsBuadxGmYk2JNRQ1OnjDo3Y22Nw
agent:uhCAk-OELMm-yJ2Kx2jF9IMh07dnG_MQfJvdFPNkT5YusX-a-dQVX
agent:uhCAkvKOu6TN3Ar6mGW84WPEBOsBuadxGmYk2JNRQ1OnjDo3Y22Nw
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:uhCAk4iQ76lk4oWGjcJnMCqJjGhEMGDY4KNQ0diZgpupME-azEbsl
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)
No scenario template for write_validated_must_get_agent_activity!
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:uhCAkHQ2BLWfQ1JeV_SknhFu91LKE9g1jsRUIuANikLG60ZcuQfta
agent:uhCAkaSQ1lAkTUNd_mQlWXk_s8o3nlvIlMPI53lybCKNeKN-ZWtS1
agent:uhCAkyBepQYdgajl76supgXn5OvbR-kS2YBzqfWlhZUw8Ni3ok7S9
get_timed_local_entries zome function.agent:uhCAk5C7vx9vSqv-zVYUySrFGSsSTbTcLOLcSpQEakmP8c-uF-D7D
agent:uhCAksbAga5wOBKaCnWSxdigKGNZJV5MdIkjwhtFMfTRqydaR59-j
agent:uhCAk5C7vx9vSqv-zVYUySrFGSsSTbTcLOLcSpQEakmP8c-uF-D7D
agent:uhCAksbAga5wOBKaCnWSxdigKGNZJV5MdIkjwhtFMfTRqydaR59-j
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:uhCAk0X-WQv3_LdSmlf4NUuLDukptTJ20yCig9Nl_0iq9TgaEYcbg
agent:uhCAk0ZUHgi3Q-damrVuEafv4y6DC1dZ00TyZqVqKm0GDoIitQ26z
agent:uhCAkEpAdoCRVl3gEqJSM9LjhwvLbr-47CPaoMMVS3v1ITdZDBNKZ
agent:uhCAkpNNXGr9XuBcNKeThcj3tAodXnIiXX8ny8dEGXIfGyKk-P7Vn
agent:uhCAkvFjIU_rs7kcHSASo-VatiCErGBuBr0hLnZAAqtKRAOcUNm7f
agent:uhCAkyxzAJdrRM7Y1bD23Y0SWAWGmpcFXa0dGD3gnW_ZyrJWAAmXG
get_timed_local_entries zome function.agent:uhCAk-2laFFC6LonKSN8tJATRW7Z7brN1rBTgfLLQthh4R8SW5C-C
agent:uhCAkRwk7oCFF4SCYL4jnBqaMouw06o5bNhLwYJemYtdDGaX3nsa3
agent:uhCAkT_hXJk3gjG17T-ZMpfITSrNoaf4Bxt1jngDRUCFOlwhOGNZZ
agent:uhCAkyHyhdLhgMOzma_Qm0kwaO6yBHwCQNwVS8VKfw4ymsmqxGh6a
agent:uhCAk-2laFFC6LonKSN8tJATRW7Z7brN1rBTgfLLQthh4R8SW5C-C
agent:uhCAkRwk7oCFF4SCYL4jnBqaMouw06o5bNhLwYJemYtdDGaX3nsa3
agent:uhCAkT_hXJk3gjG17T-ZMpfITSrNoaf4Bxt1jngDRUCFOlwhOGNZZ
agent:uhCAkyHyhdLhgMOzma_Qm0kwaO6yBHwCQNwVS8VKfw4ymsmqxGh6a
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:uhCAkFO8Q4CDd506LdSwU81pjpOuKJZ58nc5bxtiis07QgKgFXwQC
agent:uhCAkJlKA_zcJjnn19QF_1JNAoZUpD-xC0xTRhtEpfLzmMdYM_zU1
agent:uhCAkP4TN8-X_p4XC2gILJQ_5cbtEd18xNDZZPpBbN_oVvh_M7_HY
agent:uhCAkRK1ewLqfzP3AD-5YjIjU2nZXhBOVBZwaFsRRNywbukcc2psI
agent:uhCAkTpUSoTQUDc8dRXH-VfEsKnFzbkO3MGkVR1zUp8rJDU0E-7iz
agent:uhCAkeyg_f8EdYHJisNPyRzGvjmeK9PoAIMflSelU_TnNlPw6Ekgv
get_timed_local_entries zome function.agent:uhCAkMIG05b_S0t8PGEG-qix70leOoWNb0qhs6FfdiiLzkwXZTzUt
agent:uhCAkX-HZkmSH2KsSStsRWcmrqpxhoH9LBztWL8E0231lJYBtDfb5
agent:uhCAkmakGwxMAC9d1YF7uYvQBOlOj-OVHZZFnnIQSzVJHapZE9tZ8
agent:uhCAkyvYQo5oY6dK5rgB7yi9pPWrTYXBKNlL8Ta0w5jCH8Ii65p0h
agent:uhCAkMIG05b_S0t8PGEG-qix70leOoWNb0qhs6FfdiiLzkwXZTzUt
agent:uhCAkX-HZkmSH2KsSStsRWcmrqpxhoH9LBztWL8E0231lJYBtDfb5
agent:uhCAkmakGwxMAC9d1YF7uYvQBOlOj-OVHZZFnnIQSzVJHapZE9tZ8
agent:uhCAkyvYQo5oY6dK5rgB7yi9pPWrTYXBKNlL8Ta0w5jCH8Ii65p0h
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)