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 96.8%
Warning Memory growing at 287.77 MiB/s
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.5%
Warning Memory growing at 829.96 MiB/s
Critical Disk /etc/resolv.conf: 1/6 hosts above 90% capacity
Critical Heavy swap usage (23.4% swap used)
Warning 64% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-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 245.62 MiB/s
Full-Arc Create (Validated) / Zero-Arc Read
↑ Back to indexA full-arc/zero-arc mixed scenario where full-arc nodes create data that gets validated and zero-arc nodes read the data. The scenario has two roles:
full: A full-arc conductor that creates entries with a timestamp field. Those entries get validated and then retrieved by zero-arc nodes.zero: A zero-arc conductor that reads the entries created by the full-arc node(s) and records the time lag between when the entry had been created and when it was first discovered.
-
full(1 agent) -
zero(1 agent)
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 428.04 MiB/s
Critical Disk /etc/resolv.conf: 1/7 hosts above 90% capacity
Critical Heavy swap usage (24.3% swap used)
Warning 4% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/resolv.conf/nix/storeMixed 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 97.3%
Warning Memory growing at 503.74 MiB/s
Warning 14% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/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 CPU p99 reached 93.6%
Warning Memory growing at 476.19 MiB/s
Critical Disk /etc/resolv.conf: 1/6 hosts above 90% capacity
Critical Heavy swap usage (24.3% swap used)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/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 71.37 MiB/s
/etc/hostname/etc/hosts/etc/nomad.d/client-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 Memory growing at 14.17 MiB/s
//etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/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.
Warning Memory growing at 15.73 MiB/s
//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 96.6%
Warning Memory growing at 623.10 MiB/s
Critical Disk /etc/resolv.conf: 1/5 hosts above 90% capacity
Critical Heavy swap usage (23.2% swap used)
Warning 53% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-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.0%
Warning Memory growing at 336.42 MiB/s
Warning 56% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-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:uhCAk3zwCU0clYuUfFh0CpnnK2swjcV8CxTnTpx_H2N2_Cl_b0FCn
get_agent_activity_volatile_agent:uhCAk51__rNJLFkus8xhMRNy84RV89NIwZny3KcCqI1JRHHI_UbAH
get_agent_activity_volatile_agent:uhCAk6u-ywmfl5vw8zbhgNPzwb4Mw8LMUI0iVRcI9lnXWXu0wHiJl
get_agent_activity_volatile_agent:uhCAkGziaVHX7oIvnvfrjubmAIh-zxIIPrTFs-I1vRawktDCcHaXm
get_agent_activity_volatile_agent:uhCAkHS5-ADe-uA8K5EmGQiDBV8Y1eQN3jL7-W8I05bOyyMMg6yrB
get_agent_activity_volatile_agent:uhCAkKidQKv5LT_nVd8onYCUitX36cgSh8-77uJA2ReQtkK_KNjsA
get_agent_activity_volatile_agent:uhCAkM3iU1EvERW8fty_IldqN5YdDGo4T3hTU6SlSBM-P8Hu2S5-Y
get_agent_activity_volatile_agent:uhCAkOIyP6DNRtVSjjIEItE1hW5DJNw6BG0XhnMdWDuFsL9kNgb0p
get_agent_activity_volatile_agent:uhCAkTNyzuMhqp1p5olRhpLaYljo_QsnkR706D2soguw9fNYW01FG
get_agent_activity_volatile_agent:uhCAkY-C984CbNDD78iMnPzzb3s_NYMbTbwOGBTBh36B3OEZIZMNn
get_agent_activity_volatile_agent:uhCAkY9K_duO5SUCowl4UBs3Pajvri8Wx8IikXGndYaQ-8Pv3j6OL
get_agent_activity_volatile_agent:uhCAkdRq-Us8Ivp2ZKVemz8BY_jm7g_8js_72cOHM9g3QU11orMcd
get_agent_activity_volatile_agent:uhCAkdjWcj1q1OqLywQ425UKdYVn7dIG4XBDBoXaL9S3Qf0T2rePy
get_agent_activity_volatile_agent:uhCAkeQ-SXBHxqnLN9BUuPBUV-ehp0XtuDvKhjoxwe4YiPESvGdbi
get_agent_activity_volatile_agent:uhCAknNcAjMjw-WHsCKU60VFz5Ff3QD0PQ3oVeLCo4fdW8jqL-orf
get_agent_activity_volatile_agent:uhCAkqzcD3wPK8XxKzzyEVco9OAbtCLYId4Qb8PlnQ4a2F4WB96bm
get_agent_activity_volatile_agent:uhCAksBXQKDFEz7tIOiuft5g8FMIvRf6zaHy0usDRZeJHGb4NX88w
get_agent_activity_volatile_agent:uhCAkzFkpuqOHcWsliqaqjdfHeligXvNQurlPLJ0PgIolNrHvPZBu
get_agent_activity_volatile_agent:uhCAkzgGnhcm0ck65hU5sgY4gnKPaYhHwuDZ8Qi76qTGkzLOM3dHi
Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning CPU p99 reached 98.8%
Warning Memory growing at 436.10 MiB/s
Warning 16% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-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.
Warning Memory growing at 9.04 MiB/s
Write/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 99.2%
Warning Memory growing at 784.29 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 99.2%
Warning 100% of hosts overloaded (load5/ncpus > 1.0)
/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 97.8%
Warning Memory growing at 217.15 MiB/s
Warning 19% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/resolv.conf/nix/storeZero-Arc Create and Read
↑ Back to indexA 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(1 agent) -
zero_read(1 agent) -
zero_write(1 agent)
get_timed_entries_network zome function.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 451.33 MiB/s
Critical Disk /etc/resolv.conf: 1/7 hosts above 90% capacity
Critical Heavy swap usage (23.8% swap used)
Warning 12% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-meta.json/etc/resolv.conf/nix/storeZero-arc Create Data (Validated)
↑ Back to indexA 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(1 agent) -
zero(1 agent)
get_timed_local_entries zome function.Holochain MetricsClick to toggle visibility.
Host MetricsClick to toggle visibility.
Warning Memory growing at 381.13 MiB/s
Warning 8% of hosts overloaded (load5/ncpus > 1.0)
//efi-boot/etc/hostname/etc/hosts/etc/nomad.d/client-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)