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, 16 Dec 2025 10:03:35 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_20263749297
First install time
The time from conductor startup to completion of the first app installation attempt.
1.232672301s
Install app timing
The time taken to install an app.
mean 0.557822s (SD = 0.332852s)

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, 16 Dec 2025 10:03:07 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_20263749297
First install time
The time from conductor startup to completion of the first app installation attempt.
4.800117902s
Install app timing
The time taken to install an app.
mean 0.493264s (SD = 0.364547s)
Not enough time data to show a trend.

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, 16 Dec 2025 10:09:11 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_20263749297
Create rate
The average number of created records per agent.
All agents
mean 76.78/s
  • agent: uhCAkGjyneLi4wra7CozY4I356PxG5vgcP_mNbCmy5qWGJ55MyAj8
mean 70.75/s
  • agent: uhCAkIHAQnKbfTs4ZFdBuHjRKQ6gJRHwVVtOlbK4DM7grkE4Kxdwv
mean 14.14/s
  • agent: uhCAkXR5oodvjHrX1TPv31aJnbrGcquZDYa7x6NmSXkAVW_9pYK0z
mean 36.32/s
  • agent: uhCAkhksyluf_9rWIslsEbYCkULnv_2XPsf973lsfke5GKMT2KsvE
mean 124.86/s
  • agent: uhCAknefjZHaFqEeCIx8li1V2A917bMR_UGRjcDgaAIvZlzbO1QRk
mean 137.82/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 158.3697372s (SD = 27.951115s)
  • agent: uhCAk7c9ALc-viLzZkmmaIv0Rri5w6uORtl_ss5CGdG_l_6fwnAGO
mean 154.517345s (SD = 0s)
Not enough time data to show a trend.
  • agent: uhCAkBXuTcaFZqWK3wmACPaN1t8jp6Btv6nAx20qmmCEfK9VbVDI0
mean 285.903453s (SD = 12.120943s)
  • agent: uhCAkfpqoM-Fv1YQfYcZ2yKswnMCa91qDPh80jralXx0S7f1fKbUN
mean 36.732958s (SD = 27.427514s)
  • agent: uhCAkjRggsnO_CwbzgADh-Ibj0yhOgOo67ZRW2y1FZ2eXFtg3r5Ep
mean 125.114757s (SD = 69.972651s)
  • agent: uhCAksKYpHjRxiVCPzh1kBqvOFzCPWUR6bEtJdxg71BxNeUFazA_M
mean 189.580173s (SD = 30.234465s)
Sync lag rate
The average number of created records discovered per agent.
All agents
mean 106.08/s
  • agent: uhCAk7c9ALc-viLzZkmmaIv0Rri5w6uORtl_ss5CGdG_l_6fwnAGO
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkBXuTcaFZqWK3wmACPaN1t8jp6Btv6nAx20qmmCEfK9VbVDI0
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkfpqoM-Fv1YQfYcZ2yKswnMCa91qDPh80jralXx0S7f1fKbUN
mean 218.5/s
  • agent: uhCAkjRggsnO_CwbzgADh-Ibj0yhOgOo67ZRW2y1FZ2eXFtg3r5Ep
mean 35.41/s
  • agent: uhCAksKYpHjRxiVCPzh1kBqvOFzCPWUR6bEtJdxg71BxNeUFazA_M
mean 276.5/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, 16 Dec 2025 09:55:25 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_20263749297
Zome call timing
The time elapsed between start of install and calling init.
mean 0.019392s (SD = 0.013429s)

No scenario template for full_arc_create_validated_zero_arc_read!

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, 16 Dec 2025 09:56:36 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_20263749297
Send timing
The time taken to emit a batch of 10,000 signals.
mean 0.809221s (SD = 0.430992s)
Not enough time data to show a trend.
Receive timing
The time taken to receive the completed batch, to the nearest 250ms.
mean 30.810465s (SD = 0.430813s)
Not enough time data to show a trend.
Success ratio
The proportion of signals successfully received in a batch.
min 0.9484000205993652 < mean 0.9784 (SD = 0.0175) < max 0.9991000294685364

No scenario template for mixed_arc_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, 16 Dec 2025 09:57:24 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_20263749297
Dispatch timing
The time between sending a remote call and the remote handler being invoked.
All agents
mean 0.004038s (SD = 0.002483s)
  • agent: uhCAkSDVoZM6il9MPiONtDplGegscgFRjoFJ69ICfcz5s6NC1bLAa
mean 0.004035s (SD = 0.002418s)
  • agent: uhCAkac70Oshw4-QxC3Ye_7Jg6OEW4MmdBmGIMUHbRmO8AESKh1iJ
mean 0.004041s (SD = 0.002548s)
Round-trip timing
The total elapsed time to get a response to the client.
All agents
mean 0.0090455s (SD = 0.004392s)
  • agent: uhCAkSDVoZM6il9MPiONtDplGegscgFRjoFJ69ICfcz5s6NC1bLAa
mean 0.009044s (SD = 0.004354s)
  • agent: uhCAkac70Oshw4-QxC3Ye_7Jg6OEW4MmdBmGIMUHbRmO8AESKh1iJ
mean 0.009047s (SD = 0.004429s)

Remote Signals

This scenario tests the throughput of remote_signals operations.

Started
Tue, 16 Dec 2025 09:58:14 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_20263749297
Round trip time
The time from origin signal dispatch to origin receive of the remote side's response signal.
mean 0.029175s (SD = 0.023014s)
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, 16 Dec 2025 09:59:03 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_20263749297
read call timing
The time it takes to complete the zome call that retrieves the record.
mean 0.004114s (SD = 0.026248s)
read call rate (10s)
The number of zome calls made in a 10-second window.
mean 2398.07/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, 16 Dec 2025 10:14:44 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_20263749297
Session accepted -- timing
The duration of the session from acceptance to completion.
All agents
mean 0.9041005s (SD = 0.991399s)
  • agent: uhCAk-Va3_TIASamqrIX05s4aouoTAHKkCcJ9mNmg2-PDyqf4n8gd
mean 0.908637s (SD = 0.882227s)
  • agent: uhCAkvZRvvuNvM0YTxUJV9ZIN-hzerUhrsvv4BpwwTF2cFG4B-iO8
mean 0.899564s (SD = 1.10057s)
Session accepted -- success rate
The number of accepted sessions that completed per second.
All agents
mean 4.21/s
  • agent: uhCAk-Va3_TIASamqrIX05s4aouoTAHKkCcJ9mNmg2-PDyqf4n8gd
mean 4.29/s
  • agent: uhCAkvZRvvuNvM0YTxUJV9ZIN-hzerUhrsvv4BpwwTF2cFG4B-iO8
mean 4.13/s
Session accepted -- failure rate
The number of accepted sessions that failed per second.
All agents
mean -0.11000000000000032/s
  • agent: uhCAk-Va3_TIASamqrIX05s4aouoTAHKkCcJ9mNmg2-PDyqf4n8gd
mean 0.42857142857142855/s
  • agent: uhCAkvZRvvuNvM0YTxUJV9ZIN-hzerUhrsvv4BpwwTF2cFG4B-iO8
mean 0.26666666666666666/s
Session initiated -- timing
The duration of the session from initiation to completion.
  • agent: uhCAki2mWag8k93QY3bXDYxJTWW-ED1qiBS7_i11YWJtSxzS-W_gC
mean 1.19408s (SD = 1.517073s)
Session initiated -- success rate
The number of initiated sessions that completed per second.
  • agent: uhCAki2mWag8k93QY3bXDYxJTWW-ED1qiBS7_i11YWJtSxzS-W_gC
mean 8.33/s
Session initiated -- failure rate
The number of initiated sessions that failed per second.
  • agent: uhCAki2mWag8k93QY3bXDYxJTWW-ED1qiBS7_i11YWJtSxzS-W_gC
mean 0.26666666666666666/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, 16 Dec 2025 10:10:00 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_20263749297
Highest observed action_seq
The change in the highest action index on the write peer's source chain.
1708 ⬆ 8820 change: 416.3934426229508% over 686.714889112s ( 10.36/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: uhCAkNWnpYt5s-BBC9d2Dxna6B_hUzHHkSfFVGRZaCzN8PiHpq0c5
mean 0.107222s (SD = 0.040223s)
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, 16 Dec 2025 09:59: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_query_20263749297
Write timing
The time it takes to complete the zome function call that writes the entry.
mean 0.086997s (SD = 0.308175s)
Write rate
The number of writes completed per second.
mean 73.89/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, 16 Dec 2025 10:00:41 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_20263749297
Write timing
The time taken to write the entry.
mean 0.093982s (SD = 0.262435s)
Write rate
The number of writes completed per second.
mean 81.89/s
Read timing
The time taken to read the entry.
mean 0.022995s (SD = 0.017184s)
Read rate
The number of reads completed per second.
mean 81.89/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, 16 Dec 2025 10:01:30 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_20263749297
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.238817s (SD = 0.539561s)
Write rate
The number of write zome function calls that complete per second.
mean 19.74/s
Read timing
The time it takes to complete the zome function call that reads the data.
mean 0.232063s (SD = 0.5225s)
Read rate
The number of read zome function calls that complete per second.
mean 19.74/s
Error count
The number of errors accumulated over the run.
0

No scenario template for write_validated_must_get_agent_activity!

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, 16 Dec 2025 10:44:33 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_20263749297
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 72.09/s
  • agent: uhCAkTDf78Flg95YTmo0A3y0pFOOAJyeo0s4CF9nIItpstsQI_iNw
mean 35.83/s
  • agent: uhCAkUM6VyWAPAWAAd_uYd9y06UP5iS31mN2KBoFuI47ZFkscifGl
mean 43/s
  • agent: uhCAkuqWD6dzg104Nl4QsHA5_YdVHCl7IEd368g8QXWhMC_8MA_yf
mean 137.45/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 128.4406065s (SD = 47.808357s)
  • agent: uhCAk5h0ZsyXrfLE2-C7JDVxpk8reDMm-zVl9h3T51ZWAksPDjiEm
mean 126.698545s (SD = 52.370388s)
  • agent: uhCAkoNPb5sMSIfZ2BnZ-VIG1l7F5WHrBMK6pS77MhgKdEmlBvLQq
mean 130.182668s (SD = 43.246325s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 67.07/s
  • agent: uhCAk5h0ZsyXrfLE2-C7JDVxpk8reDMm-zVl9h3T51ZWAksPDjiEm
mean 71/s
  • agent: uhCAkoNPb5sMSIfZ2BnZ-VIG1l7F5WHrBMK6pS77MhgKdEmlBvLQq
mean 63.14/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 6.21 (SD = 1.77) < max 8
zero-arc
min 2 < mean 3.38 (SD = 1.54) < max 7
Error count
The number of errors accumulated across all nodes.
4

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, 16 Dec 2025 10:28:20 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_20263749297
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 75.18/s
  • agent: uhCAk-zzp3Hzxy_xb9BkfeW2-pHhEmqjCzmf_rvLs2e-EIZjBWJWC
mean 148.04/s
  • agent: uhCAk2bQRoNl7UKci_xea10IbbQt7OyujZeShdOCSRQ27D0fbVQ0l
mean 27.89/s
  • agent: uhCAk829Duq521WZiKExdSBZvh4kcLm1e6PP1-SK0PltywVmcsrVk
mean 51.3/s
  • agent: uhCAkCw2SoTd9S4LW6xzWU7RNnDcabdlK7dk_LjAIU_ARwL24ecAY
mean 125.23/s
  • agent: uhCAkItOAoLOTAOkWF1vQi9J3WgSI18XJbn7vFrPqlMZ7_ujcVd2E
mean 46.38/s
  • agent: uhCAkVOea_AKTzWhxDp36VdnsVxl2-liLo7e-KfhivBfdFGEdw9VI
mean 52.26/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 140.024518s (SD = 54.273243s)
  • agent: uhCAkN1rgMjxF_AdkEMCKNaBRp6wV7QTH8lq6ku5oIi8rVfWPkweC
mean 120.595365s (SD = 86.456914s)
  • agent: uhCAkQrPiCnvOcK5BsDuzhuLQXcFFhGoHFq1UmCJi5tEWHP6l_t9t
mean 250.234972s (SD = 24.951088s)
  • agent: uhCAkapZvQ5JnyeIVC_m2xMg1Y8SFVBGSQVH8vF7i-J3jL_Y19wKN
mean 122.92285s (SD = 76.278458s)
  • agent: uhCAkxEmDz2seZxzyaGqiEwUmnuYnb_Qna0NfvzccKzcKpZu2tdnj
mean 66.344885s (SD = 29.40651s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 54.9/s
  • agent: uhCAkN1rgMjxF_AdkEMCKNaBRp6wV7QTH8lq6ku5oIi8rVfWPkweC
mean 26/s
  • agent: uhCAkQrPiCnvOcK5BsDuzhuLQXcFFhGoHFq1UmCJi5tEWHP6l_t9t
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkapZvQ5JnyeIVC_m2xMg1Y8SFVBGSQVH8vF7i-J3jL_Y19wKN
mean 33.09/s
  • agent: uhCAkxEmDz2seZxzyaGqiEwUmnuYnb_Qna0NfvzccKzcKpZu2tdnj
mean 160.5/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 4.43 (SD = 2.25) < max 9
zero-arc
min 0 < mean 3.74 (SD = 1.25) < max 7
Error count
The number of errors accumulated across all nodes.
5

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, 16 Dec 2025 10:36:26 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_20263749297
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 76.91/s
  • agent: uhCAkNd8i0b9MZrlTVRFgUfYE5Asn6a6CEvH5tKhkFdWQg-24Lfi_
mean 30.41/s
  • agent: uhCAkWL3VgIrn7CbJuHuVSc-An2fRECL5EbxHvcrxFfrn-FBCf3uQ
mean 129.18/s
  • agent: uhCAkXo6ma1M8VJiSWpAImfKeq8T7Q32fUw4lPnvu1KotjoVc8ttW
mean 46.42/s
  • agent: uhCAkYAbcilKLmObtdTZTvFChQdcXP36bTauxmB0bLQx_tm8bsg07
mean 27.19/s
  • agent: uhCAkZ2BE85n0jEI-XnRo0VTvyPYrGEJLxYJdwOlkJ4G5UoroK_oa
mean 117.07/s
  • agent: uhCAkf7xozMhQ7AAVWZ_yPMkAaXs2hPhoZ22mhnQhWevBgBRGqJqq
mean 111.19/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 74.18709975s (SD = 22.031743s)
  • agent: uhCAk0tQqVWXLj_VcUrUB-UNNz-PtAkf6nE3rjLhCht3oI1G75Crx
mean 155.794746s (SD = 1.955278s)
Not enough time data to show a trend.
  • agent: uhCAkDEFJ12dJYxC4XlO0lWPMBM5OFXzDDjXbK5zSXzhlYyv-qqgP
mean 38.509603s (SD = 12.871022s)
  • agent: uhCAksRIE8EDZfEpVERYq6pRuKpbIKcsk6ELIdAihw0cB6iTPvVLf
mean 80.268604s (SD = 59.991427s)
  • agent: uhCAkwrjgPbEffQg1o7OL-QXWO5sHiTAsKEHbCx0Z8JIylwv8GNAb
mean 22.175446s (SD = 13.309244s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 14.75/s
  • agent: uhCAk0tQqVWXLj_VcUrUB-UNNz-PtAkf6nE3rjLhCht3oI1G75Crx
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkDEFJ12dJYxC4XlO0lWPMBM5OFXzDDjXbK5zSXzhlYyv-qqgP
mean 6/s
Not enough time data to show a trend.
  • agent: uhCAksRIE8EDZfEpVERYq6pRuKpbIKcsk6ELIdAihw0cB6iTPvVLf
mean 24.5/s
  • agent: uhCAkwrjgPbEffQg1o7OL-QXWO5sHiTAsKEHbCx0Z8JIylwv8GNAb
mean 28.5/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 5.67 (SD = 2.28) < max 9
zero-arc
min 0 < mean 4.95 (SD = 1.53) < 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, 16 Dec 2025 10:02:18 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_20263749297
Call timing
The time taken for the call to complete.
mean 0.005041s (SD = 0.052689s)
Call rate
The number of zome calls completed per second.
mean 1940.46/s
Error count
The number of errors accumulated during the run.
0