App Install
↑ Back to indexMeasure 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 1011.73 MiB/s
Warning Moderate swap usage (16.6% swap used)
/etc/hostname/etc/hosts/etc/resolv.confApp Install
↑ Back to indexMeasure 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 917.82 MiB/s
//efi-boot/nix/storeDHT Sync Lag
↑ Back to indexMeasures the lag time between an agent publishing data and other peers being able to see it. This scenario has two roles:
write: Creates entries with a timestamp field, linked to a known base hash so thatrecord_lagagents can discover them.record_lag: Repeatedly queries for links from the known base hash. When a new entry is discovered, it calculates the time difference between the entry's timestamp and the current time, giving the sync lag for that entry.
-
record_lag(1 agent) -
write(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 96.5%
Warning Memory growing at 1296.14 MiB/s
Warning 39% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeFirst Call
↑ Back to indexThis 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.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 1367.89 MiB/s
/etc/hostname/etc/hosts/etc/resolv.confLocal Signals
↑ Back to indexThis 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 135.53 MiB/s
Mixed Arc get_agent_activity
↑ Back to index
A mixed-arc scenario that measures the DHT's ability to propagate agent activity and make it available via get_agent_activity calls. The scenario has three roles:
zero_write: A zero-arc conductor that creates entries on its source chain.full_write: A full-arc conductor that creates entries on its source chain.zero_read: A zero-arc conductor that picks a random writer and repeatedly callsget_agent_activityto observe new entries appearing on the writer's chain, measuring the lag between creation and discovery.
-
full_write(1 agent) -
zero_read(1 agent) -
zero_write(1 agent)
get_agent_activity. This is measured per new action in the chain.get_agent_activity_full zome call timingget_agent_activity_full zome call that queries a writer's chain.get_agent_activity.behaviour:full_write
behaviour:zero_read
behaviour:zero_write
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 98.2%
Warning Memory growing at 280.17 MiB/s
Warning 14% of hosts overloaded (load5/ncpus > 1.0)
//boot/efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeMixed Arc must_get_agent_activity
↑ Back to index
A scenario where write agents create entries in batches of 10, while must_get_agent_activity agents each pick a random write agent and repeatedly attempt to create an entry that references the chain top of their latest batch. This reference means that the entry's validation function needs to make a must_get_agent_activity call.
The purpose of this scenario is to measure the time it takes for published agent activity data to be gossiped among authorities and become available to peers that query it via must_get_agent_activity.
This test is similar to Write Validated must_get_agent_activity, but some write agents are zero-arc and all must_get_agent_activity agents are zero-arc. This forces the must_get_agent_activity host call to go to the network.
-
full_write(1 agent) -
zero_must_get_agent_activity(1 agent) -
zero_write(1 agent)
action_seqwrite agent, aggregated across all reading agents. The reading dimension is collapsed by taking the maximum observed value for each write agent (any successful read counts as propagation). This reflects the DHT’s ability to propagate agent activity ops and make them available to querying peers.write agent's creation of a batch and a must_get_agent_activity agent's successful discovery of the batch and creation/self-validation of a new entry that depends on it.must_get_agent_activity agent was able to discover batches and create/self-validate new entries that depend on them.create_validated_sample_entry zome call timingwrite agent's source chain.must_get_agent_activity calls.behaviour:full_write
behaviour:zero_must_get_agent_activity
behaviour:zero_write
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 584.49 MiB/s
Warning 3% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeRemote Call Rate
↑ Back to indexTest 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 1044.40 MiB/s
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeRemote Signals
↑ Back to indexThis scenario tests the throughput of remote_signals operations.
-
default(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 964.62 MiB/s
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeSingle-write, many-read
↑ Back to indexCreates 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 rateHolochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
//efi-boot/nix/storeUnyt Chain Transaction
↑ Back to indexTests Unyt chain transaction system performance with credit ledger and smart agreement primitives. The scenario has three roles:
initiate: Progenitor agent that initializes the network with system templates, global configuration, and foundational smart agreementsspend: Transaction agents that accept incoming commitments and create spend transactions distributed among participantssmart_agreements: Smart agreement agents that collect RAVEs, execute agreements, and create parked link spending transactions
-
initiate(1 agent) -
smart_agreements(1 agent) -
spend(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 99.2%
Warning Memory growing at 2298.51 MiB/s
Warning 6% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeUnyt Chain Transaction Zero Arc
↑ Back to indexTests Unyt chain transaction system performance where some agents operate with a 0-arc DHT configuration. Measures data propagation between zero-arc and full-arc nodes. The scenario has five roles:
initiate: Progenitor agent that initializes the network with system templates, global configuration, and foundational smart agreementszero_spend: Zero-arc transaction agents that accept commitments and create spend transactionszero_smart_agreements: Zero-arc agents that collect RAVEs and execute smart agreementsfull_observer: Full-arc observer agents that passively monitor data propagationzero_observer: Zero-arc observer agents that passively monitor data propagation for comparison
-
full_observer(1 agent) -
initiate(1 agent) -
zero_observer(1 agent) -
zero_smart_agreements(1 agent) -
zero_spend(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 99.2%
Warning Memory growing at 2044.96 MiB/s
Warning 14% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeValidation Receipts
↑ Back to indexCreates 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 98.5%
Warning Memory growing at 890.19 MiB/s
Warning 50% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeWrite/get_agent_activity
↑ Back to index
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)
get_agent_activity_full zome call timingwrite peer's source chain.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 98.2%
Warning Memory growing at 377.18 MiB/s
Warning 28% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeWrite/get_agent_activity with volatile conductors
↑ Back to index
A scenario where write peers write entries, while get_agent_activity_volatile peers each query a single write agents activity with get_agent_activity but shutdown and restart their conductors at semi-random intervals.
Before a target write peer and the requesting get_agent_activity_volatile 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_volatile(1 agent) -
write(1 agent)
action_seqget_agent_activity. This reflects the DHT's ability to propagate agent activity ops and make them available to querying peers.get_agent_activity_full zome call timingwrite peer's source chain.get_agent_activity_volatile peers.get_agent_activity_volatile conductor.get_agent_activity_volatile conductor was running before being stopped.get_agent_activity_volatile conductor was stopped before being started again.get_agent_activity_volatile peer reach their target arc in the moment before they were shutdown.get_agent_activity_volatile_agent:uhCAk1xelptOSGO2IAk7fZxDfZe1VXdgaWneolUx9dzTIcOBGtBmR
get_agent_activity_volatile_agent:uhCAk7QMzKjCHBRsW42YbVd8W93z5nJtomCJlnOVgNiJoTcgfw0Gf
get_agent_activity_volatile_agent:uhCAkA6xnbPBc9xKHT3NOjUkpCCcR04-nwNllXJiVRFcN5WQvIo-0
get_agent_activity_volatile_agent:uhCAkAM-rSKz2thbo5iYJY6tdMcaWMiBjqnEh8RHVfzb5sQ5DFmd9
get_agent_activity_volatile_agent:uhCAkDMDGXQC0QKMiJ5T4ZX6r4AZUcpeGIfUlRZ-9eUiReiTilB_E
get_agent_activity_volatile_agent:uhCAkG8aLFXHwdKi0SRJHdZy8--86T7V_ZgKfbV6qa2Z_HCOKrxOM
get_agent_activity_volatile_agent:uhCAkHOhM0G_MRsf1g_TskueTH0QAW-GqxJAm8tfjIImjEfIJvcZ9
get_agent_activity_volatile_agent:uhCAkHsjbyl_chRt3mysgGv7rzrctsWYfEBmrqYaerUH60RN6ssP-
get_agent_activity_volatile_agent:uhCAkIPTUBsCou5uATAdU2RoWa-3tQqs9438aJg57s31G96Pbq3G3
get_agent_activity_volatile_agent:uhCAkYjF0W9ppB8pum0AUdx7l4rVazEklSNoP_coVlW7v8c66D6L6
get_agent_activity_volatile_agent:uhCAki8exqK7eU0WC2XSKHwtTGAUjo2xprxDQMCITe1LU-juk1De0
get_agent_activity_volatile_agent:uhCAkik7zWByoYTzey0EvRfuN9dw7SmZZdVYZsL8J5GnQpUKmor_E
get_agent_activity_volatile_agent:uhCAkk943Vh28NoJsGBkAyW38CpgsZBZm2G0kWesXbOQCfAnWyigQ
get_agent_activity_volatile_agent:uhCAklwU-TRAFrL0-d_MLZJqRzCDCZWEk73cJ-P9q2V9RF2vQsoSj
get_agent_activity_volatile_agent:uhCAkmC698SKf1b_iD96WHy4Fe1ai7QaAxrpklC8S70MSy4GjYX_N
get_agent_activity_volatile_agent:uhCAkotldSz6Jg1uv86gFGGooNdE01jhWaL8hdY4OWcwxf8W_l7RX
get_agent_activity_volatile_agent:uhCAks8nkskNy_oIRG8tXK1zREZIi5G8mrxQE9brs50FPb1xfm1Ya
get_agent_activity_volatile_agent:uhCAksTJEf-VTi3jEO66SGxBPZ78oOJ_bn0QIb8CKZx6H_3T05wdB
get_agent_activity_volatile_agent:uhCAkuUXr3jxjwYz89iYTEcwqv42vVAJQ8rKbNijzZd6b8yKLqkxY
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 98.7%
Warning Memory growing at 522.47 MiB/s
Critical Disk /etc/resolv.conf: 1/6 hosts above 90% capacity
Critical Heavy swap usage (34.5% swap used)
Warning 7% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeWrite/Query
↑ Back to indexCreates an entry, then queries the source chain and performs a simple operation on the entries, then repeats.
-
default(1 agent)
chain_query_count_len zome call that queries the source chain.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
//nix/storeWrite/Read
↑ Back to indexCreates an entry and reads it back, then repeats.
-
default(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
/etc/hostname/etc/hosts/etc/resolv.confWrite validated
↑ Back to indexCreates 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 85.45 MiB/s
//efi-boot/nix/storeWrite Validated must_get_agent_activity
↑ Back to index
A scenario where write agents create entries in batches of 10, while must_get_agent_activity agents each pick a random write agent and repeatedly attempt to create an entry that references the chain top of their latest batch. This reference means that the entry's validation function needs to make a must_get_agent_activity call.
The purpose of this scenario is to measure the time it takes for published agent activity data to be gossiped among authorities and become available to peers that query it via must_get_agent_activity.
This test is similar to Mixed-Arc must_get_agent_activity, but all agents are full-arc.
-
must_get_agent_activity(1 agent) -
write(1 agent)
action_seqwrite agent, aggregated across all reading agents. The reading dimension is collapsed by taking the maximum observed value for each write agent (any successful read counts as propagation). This reflects the DHT’s ability to propagate agent activity ops and make them available to querying peers.write agent's creation of a batch and a must_get_agent_activity agent's successful discovery of the batch and creation/self-validation of a new entry that depends on it.must_get_agent_activity agent was able to discover batches and create/self-validate new entries that depend on them.create_validated_sample_entry zome call timingwrite agent's source chain.must_get_agent_activity calls.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 297.87 MiB/s
Warning 7% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeZome Call, Single Value
↑ Back to indexCalls 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)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 116.31 MiB/s
/etc/hostname/etc/hosts/etc/resolv.conf