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 CPU p99 reached 95.8%
Warning 100% of hosts overloaded (load5/ncpus > 1.0)
/etc/nomad.d/client-meta.jsonApp 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 CPU p99 reached 96.7%
Warning 100% of hosts overloaded (load5/ncpus > 1.0)
/etc/nomad.d/client-meta.jsonDHT 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 98.8%
Warning Memory growing at 766.55 MiB/s
Critical Heavy swap usage (74.1% swap used)
Warning 71% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/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 1042.44 MiB/s
/etc/nomad.d/client-meta.jsonLocal 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.
/etc/nomad.d/client-meta.jsonRemote 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 CPU p99 reached 92.9%
Warning Memory growing at 2626.18 MiB/s
Critical Heavy swap usage (72.8% swap used)
/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/etc/resolv.confRemote 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 CPU p99 reached 97.3%
Warning Memory growing at 2622.74 MiB/s
Critical Heavy swap usage (72.8% swap used)
/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/etc/resolv.confSingle-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.
Warning Memory growing at 774.44 MiB/s
/etc/nomad.d/client-meta.jsonValidation 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.8%
Warning Memory growing at 635.28 MiB/s
Critical Heavy swap usage (73.1% swap used)
Warning 90% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/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.3%
Warning Memory growing at 1137.08 MiB/s
Critical Heavy swap usage (73.2% swap used)
Warning 64% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/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:uhCAk0ibjtb6ifm2arb-QTCuoj2FmkE-PgpP0Os8RfTbwPYN6uVwT
get_agent_activity_volatile_agent:uhCAk8McQ1bSugra71kOSk2yXfGI9RWxtGsHsgBvu9kY7y0xT9aoR
get_agent_activity_volatile_agent:uhCAkBQr4MxRzm98_iZLo09L7ky4PFFNuwRkK1uGQ7i1NOQLmk7fw
get_agent_activity_volatile_agent:uhCAkCWwsc-TwY3xUiX0x4IfRFhn5enmH1pHUoaCdD4RdVErozaeJ
get_agent_activity_volatile_agent:uhCAkFxiKQycnjmXJmbrc6c5LZRE0cbXJUKCREIHsNABi_RiqTHif
get_agent_activity_volatile_agent:uhCAkHHuepxWY9F-1WGBKeB2Vrz3e4wU1fKV9fIq7xEeDdbRVR0a-
get_agent_activity_volatile_agent:uhCAkI2cO2mhazqeTnGCjILhruDuRVWDutkhtH1RabxFg_P27ARW2
get_agent_activity_volatile_agent:uhCAkIGBKGoZD5gY7UOjygz3SIkG1Fag4SPERJF26XZH2k_zb1k6s
get_agent_activity_volatile_agent:uhCAkKAGz4wQSrM2BL8aCGYTXbQ-wPaQsikWYu_9bLGXKZBtr6UiM
get_agent_activity_volatile_agent:uhCAkMIlYiI2LLkH2JaNhZZjg4U_gTQm9REixjT9lbnBBLlBC4Fjo
get_agent_activity_volatile_agent:uhCAkWhLhb8m6axsdxp4ldmufZ_TubBDgoHVn75yu8L0EuxKqLKDc
get_agent_activity_volatile_agent:uhCAkWwABspndqBoDBojHb14EDSmy8jdsclpvyD5dFgDFZd6UuBVS
get_agent_activity_volatile_agent:uhCAkXHAM7n52cybuYHS5pGetj0SzNMenrcMKIYEOw_OaLIU_0Dny
get_agent_activity_volatile_agent:uhCAkmDgtekuWXkS8JYyq824tT27iSUn6kLi5TgxwRjrCsJNkdAjd
get_agent_activity_volatile_agent:uhCAkrBGNjFVZE66olXJ9FogWt6xpr9AFiuAnnyxBEiwaukJofIIv
get_agent_activity_volatile_agent:uhCAkrNjxrXIJy26NrJOQzhvhpNvOTIVaeuR8UtD6YV5tgZksujcQ
get_agent_activity_volatile_agent:uhCAksZLg1OtWglrKbXeJzAkwMf1lVZ6CUv4R7m6qtpZv46oqI1bU
get_agent_activity_volatile_agent:uhCAkuvCU9EUSXeRJbvTgDLbAmiP6WrYJ3KFil03MF2gXQUUR8thz
get_agent_activity_volatile_agent:uhCAkzEIosFyrSa9IUaYMfv7Ps21gHixUnO1FUfg-J13bY3jogami
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 99.0%
Warning Memory growing at 473.35 MiB/s
Critical Heavy swap usage (71.7% swap used)
Warning 26% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/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.
/etc/nomad.d/client-meta.jsonWrite/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.
Warning CPU p99 reached 91.4%
Warning Memory growing at 1248.74 MiB/s
/etc/nomad.d/client-meta.jsonWrite 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 CPU p99 reached 91.4%
Warning Memory growing at 1429.99 MiB/s
/etc/nomad.d/client-meta.jsonWrite 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 CPU p99 reached 96.5%
Warning Memory growing at 243.52 MiB/s
Critical Heavy swap usage (71.5% swap used)
Warning 23% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/nomad.d/meta.json/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 CPU p99 reached 94.6%
Warning Memory growing at 1000.63 MiB/s
Warning 100% of hosts overloaded (load5/ncpus > 1.0)
/etc/nomad.d/client-meta.json