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)
Warning Memory growing at 1511.56 MiB/s
Additional Host Metrics
//efi-boot/nix/storeFirst 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.Warning Memory growing at 470.32 MiB/s
Additional Host Metrics
//efi-boot/nix/storeLocal 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)
Warning Memory growing at 489.17 MiB/s
Additional Host Metrics
//nix/storeRemote 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)
Warning Memory growing at 361.66 MiB/s
Additional Host Metrics
//efi-boot/nix/storeRemote Signals
This scenario tests the throughput of remote_signals operations.
-
default(1 agent)
Additional Host Metrics
//boot/efi-boot/nix/storeSingle-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 rateWarning Memory growing at 89.58 MiB/s
Additional Host Metrics
//nix/storeTwo-party countersigning
This scenario tests the performance of countersigning operations. There are two roles: initiate and participate. The participants commit an entry to advertise that they are willing to participate in sessions. They listen for sessions and participate in one at a time.
-
initiate(1 agent) -
participate(1 agent)
Warning Memory growing at 102.68 MiB/s
Additional Host Metrics
//efi-boot/nix/storeUnyt Chain Transaction Zero Arc
Tests 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)
Additional Host Metrics
//efi-boot/nix/storeValidation 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)
Warning Memory growing at 661.19 MiB/s
Additional Host Metrics
//efi-boot/etc/hostname/etc/hosts/etc/resolv.conf/nix/storeWrite/Query
Creates 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.
Additional Host Metrics
//efi-boot/nix/storeWrite/Read
Creates an entry and reads it back, then repeats.
-
default(1 agent)
Warning Memory growing at 40.55 MiB/s
Additional Host Metrics
//efi-boot/nix/storeWrite 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)
Warning Memory growing at 73.32 MiB/s
Additional Host Metrics
//efi-boot/nix/store