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.

Started
Tue, 23 Dec 2025 16:31:53 UTC
Peer count
1
Peer count at end
1
Behaviours
  • large (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
app_install_large_20465740959
First install time
The time from conductor startup to completion of the first app installation attempt.
0.218110662s
Install app timing
The time taken to install an app.
mean 0.066654s (SD = 0.022369s)

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.

Started
Tue, 23 Dec 2025 16:33:47 UTC
Peer count
1
Peer count at end
1
Behaviours
  • minimal (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
app_install_minimal_20465740959
First install time
The time from conductor startup to completion of the first app installation attempt.
0.266001838s
Install app timing
The time taken to install an app.
mean 0.072867s (SD = 0.025552s)

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 metric ws.custom.dht_sync_sent_count is 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 called wt.custom.dht_sync_lag.

After each behaviour loop the metric ws.custom.dht_sync_recv_count is incremented.

Started
Tue, 23 Dec 2025 16:35:55 UTC
Peer count
10
Peer count at end
10
Behaviours
  • record_lag (5 agents)
  • write (5 agents)
Wind Tunnel version
0.5.0-dev.0
Run ID
dht_sync_lag_20465740959
Create rate
The average number of created records per agent.
All agents
mean 105.77/s
  • agent: uhCAkF8b4eM4ip09sCzTZn-R643QP5xUs2yBDf222OaRYiK8BtgXS
mean 118.36/s
  • agent: uhCAkU-Hnx08phSOKZPQiEqBUTkLMQAB_1gk5xcQhrwf1UEw80abn
mean 227.39/s
  • agent: uhCAkcJnrrtf_EFHie3E8AsQKteLhpmeZh4Xoq1v9A8WvD7pUBhGV
mean 117.46/s
  • agent: uhCAkwTk3sPDEDUGwNNVkczwoini5wVG59sXlrCMDYAhf0tl9dtbc
mean 17.79/s
  • agent: uhCAkwtGjaDtoFe6CAp4bpbkU7_Nd0LyN_XDfD5r9xDJoLXh8RY2Q
mean 47.83/s
Sync lag timing
The average time between when a record was created and when it is first seen by an agent.
All agents
mean 154.426967s (SD = 37.125442s)
  • agent: uhCAk-CQjKzSSYQRZnrsUvQq39zB3DT_TvinmW_RbwO8UE5sZE_yI
mean 86.178547s (SD = 32.507225s)
  • agent: uhCAkkoGEIiuW8TnRfy6VP_MzsBah6iuowvgEQ_UCDtZDA-6XSLY7
mean 340.869402s (SD = 38.541962s)
  • agent: uhCAknoWM0T3pcq9RNNUykeu21mCNYc3ReHrwLj77kTiUF-SQxKzD
mean 109.959145s (SD = 38.391699s)
  • agent: uhCAkpP9SO5Vyxx3FRcOwvhCi9EgMaOK020tQHwyl4TiPLMaj2zGn
mean 96.247967s (SD = 30.307681s)
  • agent: uhCAky9h-MDazJXyUy2LdTmCxVCugk-GBruiaazjkBc_0SL6ppDll
mean 138.879775s (SD = 45.878644s)
Sync lag rate
The average number of created records discovered per agent.
All agents
mean 78.07/s
  • agent: uhCAk-CQjKzSSYQRZnrsUvQq39zB3DT_TvinmW_RbwO8UE5sZE_yI
mean 231.75/s
  • agent: uhCAkkoGEIiuW8TnRfy6VP_MzsBah6iuowvgEQ_UCDtZDA-6XSLY7
mean 46.11/s
  • agent: uhCAknoWM0T3pcq9RNNUykeu21mCNYc3ReHrwLj77kTiUF-SQxKzD
mean 18.91/s
  • agent: uhCAkpP9SO5Vyxx3FRcOwvhCi9EgMaOK020tQHwyl4TiPLMaj2zGn
mean 35.9/s
  • agent: uhCAky9h-MDazJXyUy2LdTmCxVCugk-GBruiaazjkBc_0SL6ppDll
mean 57.67/s
Error count
The number of errors encountered during the scenario.
2

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.

Started
Tue, 23 Dec 2025 16:13:12 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
first_call_20465740959
Zome call timing
The time elapsed between start of install and calling init.
mean 0.024139s (SD = 0.053628s)

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.

Started
Tue, 23 Dec 2025 16:15:23 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
local_signals_20465740959
Send timing
The time taken to emit a batch of 10,000 signals.
mean 1.217109s (SD = 0.582337s)
Not enough time data to show a trend.
Receive timing
The time taken to receive the completed batch, to the nearest 250ms.
mean 31.218461s (SD = 0.582633s)
Not enough time data to show a trend.
Success ratio
The proportion of signals successfully received in a batch.
min 0.8632000088691711 < mean 0.9396 (SD = 0.0409) < max 0.973900020122528

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.

Started
Tue, 23 Dec 2025 16:17:23 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
remote_call_rate_20465740959
Dispatch timing
The time between sending a remote call and the remote handler being invoked.
All agents
mean 0.003072s (SD = 0.010061s)
  • agent: uhCAkGJ9QbrI-TioiaXy2mnzEoh-vIA4pwD97JP-0g0v4ZCZ_dFgO
mean 0.003035s (SD = 0.008396s)
  • agent: uhCAkRJmOV5d2E7xFq780dfePKymN5k9vKMfurgmIKT-BXanRd-2v
mean 0.003108s (SD = 0.011726s)
Round-trip timing
The total elapsed time to get a response to the client.
All agents
mean 0.007564s (SD = 0.028212s)
  • agent: uhCAkGJ9QbrI-TioiaXy2mnzEoh-vIA4pwD97JP-0g0v4ZCZ_dFgO
mean 0.007562s (SD = 0.028393s)
  • agent: uhCAkRJmOV5d2E7xFq780dfePKymN5k9vKMfurgmIKT-BXanRd-2v
mean 0.007566s (SD = 0.028031s)

Remote Signals

This scenario tests the throughput of remote_signals operations.

Started
Tue, 23 Dec 2025 16:19:20 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
remote_signals_20465740959
Round trip time
The time from origin signal dispatch to origin receive of the remote side's response signal.
mean 0.019968s (SD = 0.02604s)
Timeouts
The number of timeouts waiting for the remote side's response signal (default timeout is 20 seconds).
0

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.

Started
Tue, 23 Dec 2025 16:21:29 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
single_write_many_read_20465740959
read call timing
The time it takes to complete the zome call that retrieves the record.
mean 0.005179s (SD = 0.00092s)
read call rate (10s)
The number of zome calls made in a 10-second window.
mean 1909.39/10s
Error count
The number of errors collected.
0

Two-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.

Started
Tue, 23 Dec 2025 16:42:11 UTC
Peer count
3
Peer count at end
3
Behaviours
  • initiate (1 agent)
  • participate (2 agents)
Wind Tunnel version
0.5.0-dev.0
Run ID
two_party_countersigning_20465740959
Session accepted -- timing
The duration of the session from acceptance to completion.
All agents
mean 0.602365s (SD = 0.520261s)
  • agent: uhCAkGt5goA4sVjMJuzLJE4aFuciq-pBmwQJKo4rVeqyVqprYSx_s
mean 0.753415s (SD = 0.815101s)
  • agent: uhCAkQIM8wraBPm80QJWCpS5tT_BXgtn2vOI8si9V-_6S2_48FOlb
mean 0.451314s (SD = 0.22542s)
Session accepted -- success rate
The number of accepted sessions that completed per second.
All agents
mean 6.72/s
  • agent: uhCAkGt5goA4sVjMJuzLJE4aFuciq-pBmwQJKo4rVeqyVqprYSx_s
mean 6.95/s
  • agent: uhCAkQIM8wraBPm80QJWCpS5tT_BXgtn2vOI8si9V-_6S2_48FOlb
mean 6.48/s
Session accepted -- failure rate
The number of accepted sessions that failed per second.
All agents
mean -0.13999999999999968/s
  • agent: uhCAkGt5goA4sVjMJuzLJE4aFuciq-pBmwQJKo4rVeqyVqprYSx_s
mean 1.3157894736842106/s
  • agent: uhCAkQIM8wraBPm80QJWCpS5tT_BXgtn2vOI8si9V-_6S2_48FOlb
mean 0.5714285714285714/s
Session initiated -- timing
The duration of the session from initiation to completion.
  • agent: uhCAkruFEqRtED-S0PVH_G4LD5bbiDs8izz0yPNFyLHbY1O-zZom5
mean 0.758803s (SD = 0.921072s)
Session initiated -- success rate
The number of initiated sessions that completed per second.
  • agent: uhCAkruFEqRtED-S0PVH_G4LD5bbiDs8izz0yPNFyLHbY1O-zZom5
mean 13/s
Session initiated -- failure rate
The number of initiated sessions that failed per second.
  • agent: uhCAkruFEqRtED-S0PVH_G4LD5bbiDs8izz0yPNFyLHbY1O-zZom5
mean 0.47619047619047616/s

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.

Started
Tue, 23 Dec 2025 16:38:08 UTC
Peer count
2
Peer count at end
2
Behaviours
  • get_agent_activity (1 agent)
  • write (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
write_get_agent_activity_20465740959
Highest observed action_seq
The change in the highest action index on the write peer's source chain.
832 ⬆ 4029 change: 384.25480769230774% over 827.827517587s ( 3.86/s)
get_agent_activity_full zome call timing
The time taken to call the zome function that retrieves information on a write peer's source chain.
  • agent: uhCAkBQhWRhndAQa4RS6SY2BWaxj6m1r_KiYAfOsMLgtkpSMaJkdg
mean 0.049399s (SD = 0.104538s)
Error count
The number of errors accumulated.
0

Write/Query

Creates an entry, then queries the source chain and performs a simple operation on the entries, then repeats.

Started
Tue, 23 Dec 2025 16:23:42 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
write_query_20465740959
Write timing
The time it takes to complete the zome function call that writes the entry.
mean 0.092567s (SD = 0.242359s)
Write rate
The number of writes completed per second.
mean 72.75/s
Error count
The number of errors accumulated during the run.
0

Write/Read

Creates an entry and reads it back, then repeats.

Started
Tue, 23 Dec 2025 16:25:54 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
write_read_20465740959
Write timing
The time taken to write the entry.
mean 0.065254s (SD = 0.112765s)
Write rate
The number of writes completed per second.
mean 93.04/s
Read timing
The time taken to read the entry.
mean 0.038996s (SD = 0.022949s)
Read rate
The number of reads completed per second.
mean 93/s
Error count
The number of errors accumulated over the run.
0

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.

Started
Tue, 23 Dec 2025 16:27:53 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
write_validated_20465740959
Write timing
The time it takes to complete the zome function call that writes the entry, updates it, and links to the update.
mean 0.058155s (SD = 0.028334s)
Write rate
The number of write zome function calls that complete per second.
mean 75.32/s
Read timing
The time it takes to complete the zome function call that reads the data.
mean 0.075061s (SD = 0.025609s)
Read rate
The number of read zome function calls that complete per second.
mean 75.32/s
Error count
The number of errors accumulated over the run.
0

Write Validated must_get_agent_activity

A scenario where write agents create entries, while must_get_agent_activity agents create entries which are validated with a must_get_agent_activity call for a single write agent's activity.

Before a target write peer and the requesting peer are in sync, the must_get_agent_activity request will go over the network. Once a write peer reaches sync with the requesting must_get_agent_activity peer, the write peer will publish their actions and entries, and so the must_get_agent_activity calls will likely have the data it needs locally. At that point this measures the database query performance and code paths through host functions.

Started
Tue, 23 Dec 2025 16:40:08 UTC
Peer count
2
Peer count at end
2
Behaviours
  • must_get_agent_activity (1 agent)
  • write (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
write_validated_must_get_agent_activity_20465740959
Highest observed action_seq
The change in the must_get_agent_activity peer's source chain top over the run.
16 ⬆ 1864 change: 11550% over 818.657452312s ( 2.26/s)
create_validated_sample_entry zome call timing
The time taken to complete the zome function call that creates the entry that depends on a write agent's source chain.
  • agent: uhCAkD7RLvBC_0g8DmZoR-6Rc8KHehW6KHXXZcs-rBUiVeLrxjZMP
mean 0.104004s (SD = 0.140491s)
Error count
The number of errors accumulated over the run.
54224

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 that zero_read nodes 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.
Started
Tue, 23 Dec 2025 16:51:44 UTC
Peer count
9
Peer count at end
9
Behaviours
  • full (3 agents)
  • zero_read (3 agents)
  • zero_write (3 agents)
Wind Tunnel version
0.5.0-dev.0
Run ID
zero_arc_create_and_read_20465740959
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 102.03/s
  • agent: uhCAkeB5r27AP3DeaDWKkz2oQq5seOQAwjlJLqekFGaYHz1OOMH4J
mean 34.09/s
  • agent: uhCAkhpprDgI2IXQwlLONuntP7D8mGv5YwTcawBbARLsEz4A5gKIq
mean 135.86/s
  • agent: uhCAklLugl8cycdmuDIQD5k4ecBbBmtgHtHihaT6qkOchXRN2_CJF
mean 136.14/s
Sync lag timing
For each entry, the time lag between when it was created and when the full-arc node could read it via the get_timed_local_entries zome function.
All agents
mean 263.579724s (SD = 22.583954s)
  • agent: uhCAkCe6tGMr0xL3LLfo2li9lHYdzwASXpYqaO1JypLnyvRK3PSRv
mean 33.372439s (SD = 2.849473s)
Not enough time data to show a trend.
  • agent: uhCAknM7P6dzvavefknrhvcUWsEu9HO_VKVKbaCTw1O9psmGNIVk3
mean 608.435088s (SD = 5.702481s)
Not enough time data to show a trend.
  • agent: uhCAkoe9Ebp2evaBjWC3NgTl9tCD5qphvVXNzaXhDWIwjLHaE81o-
mean 148.931644s (SD = 59.199908s)
Not enough time data to show a trend.
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 0/s
  • agent: uhCAkCe6tGMr0xL3LLfo2li9lHYdzwASXpYqaO1JypLnyvRK3PSRv
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAknM7P6dzvavefknrhvcUWsEu9HO_VKVKbaCTw1O9psmGNIVk3
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkoe9Ebp2evaBjWC3NgTl9tCD5qphvVXNzaXhDWIwjLHaE81o-
mean 0/s
Not enough time data to show a trend.
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 3.03 (SD = 3.17) < max 7
zero-arc
min 3 < mean 5.51 (SD = 1.11) < max 7
Error count
The number of errors accumulated across all nodes.
7

Zero-Arc Create Data

A zero-arc/full-arc mixed scenario where zero-arc nodes create data 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.
Started
Tue, 23 Dec 2025 16:44:13 UTC
Peer count
10
Peer count at end
10
Behaviours
  • full (4 agents)
  • zero (6 agents)
Wind Tunnel version
0.5.0-dev.0
Run ID
zero_arc_create_data_20465740959
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 69.04/s
  • agent: uhCAk7QFAYS7s47icn5ZNn9BAOm1SFAM3leVnUBa57KNEl-OaUR8q
mean 54.67/s
  • agent: uhCAkPuwf9tPOii2-me1T47BeJYh1wP0V7Qc078n6QsClsnclVgJE
mean 188.83/s
  • agent: uhCAkQq46jDe6qqe9dgulJvCQUSbCxdK4_YuV0tzGONo298P3L5mA
mean 24.64/s
  • agent: uhCAkUDf-jo7uMN1xYpM0_Rbm0_b8rs3EkrVge0Nbwen8ETb7fdIo
mean 48.64/s
  • agent: uhCAkdJeduiG9AaCu6T7Xk6kMhT43g4XC85QIRwn7_H0pO6Knsg7l
mean 49.91/s
  • agent: uhCAktb-HhLL3QQ4oLSa2v8bD2QndZyO5G6jpaAsFtMwXG0qdsnQC
mean 47.55/s
Sync lag timing
For each entry, the time lag between when it was created and when the full-arc node could read it via the get_timed_local_entries zome function.
All agents
mean 1.3685282035089008e+32s (SD = 1.5006067871195947e+32s)
  • agent: uhCAkhlFqatqGdzHPcwBnHEjSb2n42vLw_vktCiVy4ZuIan-THegl
mean 4.575418311977483e+31s (SD = 1.1608572890572353e+32s)
  • agent: uhCAkjXeMBfMAvRpj7H0Kkb2IpK0RJkWjNi9GxVYaRdViHLsBKWjJ
mean 1.1342745564031286e+32s (SD = 1.6041064611200304e+32s)
  • agent: uhCAkp_GoTJ5wb3NfM-kGLGrgvIFHXPPAJYY_d9CLJnataG4Jv88J
mean 1.4803032481692806e+32s (SD = 1.6869834687801287e+32s)
  • agent: uhCAkvovjZHdZOOwkE6wsnyFToAyp0NDV9oG19uUbGJG8rf0OYAel
mean 2.401993178265446e+32s (SD = 1.5504799295209844e+32s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 107.94/s
  • agent: uhCAkhlFqatqGdzHPcwBnHEjSb2n42vLw_vktCiVy4ZuIan-THegl
mean 237/s
  • agent: uhCAkjXeMBfMAvRpj7H0Kkb2IpK0RJkWjNi9GxVYaRdViHLsBKWjJ
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkp_GoTJ5wb3NfM-kGLGrgvIFHXPPAJYY_d9CLJnataG4Jv88J
mean 194.75/s
  • agent: uhCAkvovjZHdZOOwkE6wsnyFToAyp0NDV9oG19uUbGJG8rf0OYAel
mean 0/s
Not enough time data to show a trend.
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 4.2 (SD = 2.65) < max 9
zero-arc
min 5 < mean 6.9 (SD = 1.27) < max 9
Error count
The number of errors accumulated across all nodes.
0

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.
Started
Tue, 23 Dec 2025 16:49:37 UTC
Peer count
10
Peer count at end
10
Behaviours
  • full (4 agents)
  • zero (6 agents)
Wind Tunnel version
0.5.0-dev.0
Run ID
zero_arc_create_data_validated_20465740959
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 113.79/s
  • agent: uhCAk1sycuFtW4QmfdOdO2_obLlcEoFXOjLOCgoFTT9x2aG1QbQRV
mean 40.29/s
  • agent: uhCAk7E-ra8tDFJ9ubqAhHo6xq8zgd6Ns7kyFSH_MkCXQG5B14wRU
mean 50.21/s
  • agent: uhCAkhYmg-seAuNnRX89FynxvmI4R1G0wUSX2r45PiMk8qxJCsKOd
mean 148.31/s
  • agent: uhCAkj-Mltq4wKxkcLwvL50N9eJSFkFCGvv3w6GIGnoqKscJp7mWW
mean 188.77/s
  • agent: uhCAkrRmL9R3zKRhYzIzwVpwLSltfb6sgKVBsNTkiVwKMhQAa-U5e
mean 142.92/s
  • agent: uhCAkzmPKcgwqOXpaxexIVX4WF8Pp2q2bmVCKX0sSGKcXd0N059yL
mean 112.23/s
Sync lag timing
For each entry, the time lag between when it was created and when the full-arc node could read it via the get_timed_local_entries zome function.
All agents
mean 195.485523s (SD = 6.857632s)
  • agent: uhCAkK6ug5U1IPLC28Ws0xcrTX2m5HAKW-RUtYue6TA8IutmjVwkM
mean 64.647712s (SD = 16.995441s)
Not enough time data to show a trend.
  • agent: uhCAkP3JhJaeoclji75PRgJDZuFZ8YFqPndj6_WXYkWe7PvEgK8vb
mean 700.657798s (SD = 0s)
Not enough time data to show a trend.
  • agent: uhCAkTzhonqcSqSEEqStqV4mAsWENF3REcVpULerYIlpE-Of5E2y-
mean 15.193302s (SD = 10.435088s)
  • agent: uhCAkvC-Q0MwdwFfOfnOp25bHWPIBsuwXkAheUZ9Guxuhgmgu4k9q
mean 1.443282s (SD = 0s)
Not enough time data to show a trend.
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 45.67/s
  • agent: uhCAkK6ug5U1IPLC28Ws0xcrTX2m5HAKW-RUtYue6TA8IutmjVwkM
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkP3JhJaeoclji75PRgJDZuFZ8YFqPndj6_WXYkWe7PvEgK8vb
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkTzhonqcSqSEEqStqV4mAsWENF3REcVpULerYIlpE-Of5E2y-
mean 182.67/s
  • agent: uhCAkvC-Q0MwdwFfOfnOp25bHWPIBsuwXkAheUZ9Guxuhgmgu4k9q
mean 0/s
Not enough time data to show a trend.
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 6.66 (SD = 2.41) < max 9
zero-arc
min 4 < mean 8.08 (SD = 1.09) < max 9
Error count
The number of errors accumulated across all nodes.
0

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.

Started
Tue, 23 Dec 2025 16:29:52 UTC
Peer count
1
Peer count at end
1
Behaviours
  • Default (1 agent)
Wind Tunnel version
0.5.0-dev.0
Run ID
zome_call_single_value_20465740959
Call timing
The time taken for the call to complete.
mean 0.00452s (SD = 0.000856s)
Call rate
The number of zome calls completed per second.
mean 2188.96/s
Error count
The number of errors accumulated during the run.
0