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
Mon, 22 Dec 2025 20:59:39 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_20442873999
First install time
The time from conductor startup to completion of the first app installation attempt.
0.38078473s
Install app timing
The time taken to install an app.
mean 0.111004s (SD = 0.02587s)

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
Mon, 22 Dec 2025 21:01:50 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_20442873999
First install time
The time from conductor startup to completion of the first app installation attempt.
0.832505821s
Install app timing
The time taken to install an app.
mean 0.890153s (SD = 0.725585s)

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
Mon, 22 Dec 2025 21:03:54 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_20442873999
Create rate
The average number of created records per agent.
All agents
mean 99.57/s
  • agent: uhCAk0oQ3pDzIw2J1Yef2tn7UPccik0tCSwn4Pb79eNt0vXHDj4Fv
mean 54.64/s
  • agent: uhCAk2EJfWGBiRuW0u04g8S87mcncqA-r3iJBtw-ZRU6f9fudbhE2
mean 21.9/s
  • agent: uhCAk4toQ7_9mOpLRF7rhSa9_hO-qP8dNt7VZihagMr6zpSLGu0R3
mean 159.21/s
  • agent: uhCAkBDtvyDWqQ_GvyVTLmmmGmGAQRa2SKHnrSRI486-EhwdB2vJJ
mean 244.45/s
  • agent: uhCAksbQ64yfC0NkVwV8KW0rUxug3GZTsLf7IqFuW5wgOIjKg-n_v
mean 17.67/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 237.440406s (SD = 40.92078s)
  • agent: uhCAk8iZaq94j7BcpKGh26AxdP6xjPKVqV_TFQM2IbrsDOS1BZItb
mean 50.619356s (SD = 42.194807s)
  • agent: uhCAkEzaPVufvl-7YOqSkONHGeO6hiT2o3njnvNp95i2IhXXEZo8T
mean 95.468184s (SD = 32.988407s)
  • agent: uhCAkO8S5o9hXhlEfHK_c61x0wdFGcR-VtYWmV7J-APnLHuDrj1k8
mean 760.913273s (SD = 17.06576s)
  • agent: uhCAkTzhqqXXXhoTX1q3W12WuAGloRD_q-tnYZrkyjLhv5x07ypXa
mean 232.524549s (SD = 71.910757s)
  • agent: uhCAkffg9FiqH0CdmJHMbFHJxIFM8HqxddJXZLtckbltCIjNOU4w4
mean 47.676668s (SD = 40.444169s)
Sync lag rate
The average number of created records discovered per agent.
All agents
mean 156.55/s
  • agent: uhCAk8iZaq94j7BcpKGh26AxdP6xjPKVqV_TFQM2IbrsDOS1BZItb
mean 186.36/s
  • agent: uhCAkEzaPVufvl-7YOqSkONHGeO6hiT2o3njnvNp95i2IhXXEZo8T
mean 15.67/s
  • agent: uhCAkO8S5o9hXhlEfHK_c61x0wdFGcR-VtYWmV7J-APnLHuDrj1k8
mean 148.5/s
  • agent: uhCAkTzhqqXXXhoTX1q3W12WuAGloRD_q-tnYZrkyjLhv5x07ypXa
mean 77/s
Not enough time data to show a trend.
  • agent: uhCAkffg9FiqH0CdmJHMbFHJxIFM8HqxddJXZLtckbltCIjNOU4w4
mean 355.2/s
Error count
The number of errors encountered during the scenario.
1

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
Mon, 22 Dec 2025 20:41: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_20442873999
Zome call timing
The time elapsed between start of install and calling init.
mean 0.020391s (SD = 0.004063s)

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
Mon, 22 Dec 2025 20:43:22 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_20442873999
Send timing
The time taken to emit a batch of 10,000 signals.
mean 0.706046s (SD = 0.548957s)
Not enough time data to show a trend.
Receive timing
The time taken to receive the completed batch, to the nearest 250ms.
mean 30.707122s (SD = 0.548802s)
Not enough time data to show a trend.
Success ratio
The proportion of signals successfully received in a batch.
min 0.028999999165534973 < mean 0.507 (SD = 0.37) < max 0.9835000038146972

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
Mon, 22 Dec 2025 20:45:26 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_20442873999
Dispatch timing
The time between sending a remote call and the remote handler being invoked.
All agents
mean 0.002199s (SD = 0.003599s)
  • agent: uhCAkRoLjW1t_OXjbwxhBWXfXqcDo2Ntw64B9ZuYDrmri2FSLxIBs
mean 0.0022s (SD = 0.00339s)
  • agent: uhCAkyfP-okYtzN28fF7t7XFAHOJaImv8ENZCF-L-77YCSHF6GZ5o
mean 0.002197s (SD = 0.003808s)
Round-trip timing
The total elapsed time to get a response to the client.
All agents
mean 0.004832s (SD = 0.005766s)
  • agent: uhCAkRoLjW1t_OXjbwxhBWXfXqcDo2Ntw64B9ZuYDrmri2FSLxIBs
mean 0.004825s (SD = 0.006348s)
  • agent: uhCAkyfP-okYtzN28fF7t7XFAHOJaImv8ENZCF-L-77YCSHF6GZ5o
mean 0.004839s (SD = 0.005183s)

Remote Signals

This scenario tests the throughput of remote_signals operations.

Started
Mon, 22 Dec 2025 20:47:26 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_20442873999
Round trip time
The time from origin signal dispatch to origin receive of the remote side's response signal.
mean 0.025867s (SD = 0.024914s)
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
Mon, 22 Dec 2025 20:49:30 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_20442873999
read call timing
The time it takes to complete the zome call that retrieves the record.
mean 0.00193s (SD = 0.002366s)
read call rate (10s)
The number of zome calls made in a 10-second window.
mean 5139.62/10s
Error count
The number of errors collected.
0

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
Mon, 22 Dec 2025 21:05:52 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_20442873999
Highest observed action_seq
The change in the highest action index on the write peer's source chain.
438 ⬆ 2978 change: 579.9086757990867% over 828.983296385s ( 3.06/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: uhCAkGnOcuh1mj3kNnLuCEAZ6YWKlRmVB2X1Kkd8gVHopu4Ld4Uk2
mean 0.039174s (SD = 0.092586s)
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
Mon, 22 Dec 2025 20:51:32 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_20442873999
Write timing
The time it takes to complete the zome function call that writes the entry.
mean 0.089103s (SD = 0.239392s)
Write rate
The number of writes completed per second.
mean 71.85/s
Error count
The number of errors accumulated during the run.
0

Write/Read

Creates an entry and reads it back, then repeats.

Started
Mon, 22 Dec 2025 20:53:26 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_20442873999
Write timing
The time taken to write the entry.
mean 0.060613s (SD = 0.145388s)
Write rate
The number of writes completed per second.
mean 107.14/s
Read timing
The time taken to read the entry.
mean 0.031417s (SD = 0.017744s)
Read rate
The number of reads completed per second.
mean 107.11/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
Mon, 22 Dec 2025 20:55:26 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_20442873999
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.195437s (SD = 0.440881s)
Write rate
The number of write zome function calls that complete per second.
mean 22.11/s
Read timing
The time it takes to complete the zome function call that reads the data.
mean 0.236361s (SD = 0.447982s)
Read rate
The number of read zome function calls that complete per second.
mean 22.07/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
Mon, 22 Dec 2025 21:07:48 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_20442873999
Highest observed action_seq
The change in the must_get_agent_activity peer's source chain top over the run.
16 ⬆ 1556 change: 9625% over 803.406910428s ( 1.92/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: uhCAkTBlhBt8EJIq57YZmMHMyxyjAns5pWoabReMnMr7AIyQlCcMq
mean 0.040071s (SD = 0.016403s)
Error count
The number of errors accumulated over the run.
87545

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
Mon, 22 Dec 2025 21:15:17 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_20442873999
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 159.31/s
  • agent: uhCAkINHNtN1P8MOz-u8Mlh0U9N5ZPZtDeIVlUpdFy2kEdc9PfRHM
mean 151.57/s
  • agent: uhCAkYyvL5jIdN2ckuaX_ifepvlBgQIK1Du7EkqllrOaunZ8XVUsI
mean 158.73/s
  • agent: uhCAkcbIdQMJSP5g124bsQm8O_xOEXMoZ1c_yiM1uRYDhn8_eui1Q
mean 167.62/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 9.320777876530041e+31s (SD = 8.468052765830284e+31s)
  • agent: uhCAklLU5r7rrFPO-ilZbVfrf2h78Y1Nn5RApT6f5RYR7A-Fztx_R
mean 1.8641555753060082e+32s (SD = 1.6936105531660567e+32s)
Not enough time data to show a trend.
  • agent: uhCAkoih_9_JxNjcVNycD5EW576TirgiO_D-wjqgMvPyaPaNOXYah
mean 788.736337s (SD = 29.508125s)
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: uhCAklLU5r7rrFPO-ilZbVfrf2h78Y1Nn5RApT6f5RYR7A-Fztx_R
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkoih_9_JxNjcVNycD5EW576TirgiO_D-wjqgMvPyaPaNOXYah
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 5.77 (SD = 2.3) < max 8
zero-arc
min 4 < mean 4.79 (SD = 0.79) < max 7
Error count
The number of errors accumulated across all nodes.
5

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
Mon, 22 Dec 2025 21:09:47 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_20442873999
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 81.38/s
  • agent: uhCAkE9Yhe0KcT5cWYK5BAmR7Ou5fHpsWJvl1WABna3e6GImMWdz0
mean 123.11/s
  • agent: uhCAkGtBDRLwW9W5UwGfFEruzir_-jXTuST6B6WjwTNARMSfNE-1Q
mean 24.07/s
  • agent: uhCAkIDcZDnqzxdCPRyTcjViWB2GcRrM_c9dIuK5GERKQotWLZYV9
mean 134.39/s
  • agent: uhCAkVC5xqYU-8oN31Auidu2ehFf8FBBamyotZ1bRG-2K6o74Ob0g
mean 39.04/s
  • agent: uhCAkhBrqTaieiOA_9kVMzkwOIma-VkLRHD2rkjqhkBcn27K8nJ7E
mean 110.04/s
  • agent: uhCAkmQNlbAo1YzAwTYuXvG56CI_ba6xKCIiI25UMrYjthOeE73z8
mean 57.63/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 63.72227s (SD = 31.818271s)
  • agent: uhCAkQTnztmxDZKo7-qN9U5jiqCeLN7FHnocClpCNtqWn1uGVo4io
mean 40.680381s (SD = 21.399647s)
  • agent: uhCAkadMlwA2RRWcgCT2DS5OtsBvrEgk0A4zxcZDci81VHChiuhQA
mean 42.517356s (SD = 21.923186s)
  • agent: uhCAkf9G8NXG14MIIfNCv6hbUO99b69isfjXCAdGM8BdHscVHJhft
mean 110.241937s (SD = 43.272777s)
  • agent: uhCAktJPfabsL2TD0mYEogLZKLa3SVRQ0nZyIJ9fGhEV8n44Crpua
mean 61.449406s (SD = 40.677476s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 89.55/s
  • agent: uhCAkQTnztmxDZKo7-qN9U5jiqCeLN7FHnocClpCNtqWn1uGVo4io
mean 184.17/s
  • agent: uhCAkadMlwA2RRWcgCT2DS5OtsBvrEgk0A4zxcZDci81VHChiuhQA
mean 124.33/s
  • agent: uhCAkf9G8NXG14MIIfNCv6hbUO99b69isfjXCAdGM8BdHscVHJhft
mean 12.22/s
  • agent: uhCAktJPfabsL2TD0mYEogLZKLa3SVRQ0nZyIJ9fGhEV8n44Crpua
mean 37.46/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 2.98 (SD = 2.45) < max 9
zero-arc
min 0 < mean 3.71 (SD = 1.71) < 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
Mon, 22 Dec 2025 21:11:54 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_20442873999
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 41.28/s
  • agent: uhCAk3VcxqTLG4bh5DNOZ9BGJSDYylMfcQao1RN9VqwMZSE2M-ZhT
mean 37.15/s
  • agent: uhCAkFpFoaVUWrLP09mpd__vgInyw8ZeEWk6TnhzrWcS88jYfP6Jz
mean 15/s
  • agent: uhCAkQSPtrfs9h-rSMCjjt-6G6xF-VCB7K5q-mWvQQm4WyFkevaLj
mean 20.38/s
  • agent: uhCAkQeygKKGMxaMP2gdSFVWiz2ra-QSp6-9TJraQ_-N1UxO9OkqF
mean 116/s
  • agent: uhCAka5GzeU6bKjZA5sQujAt5AMLCjL7unaGnWDsaEKyT-LQ4Oj5B
mean 39.11/s
  • agent: uhCAkaWk_ie5pcCwUd22PgeEUqI4AFSAPT8JrUWoTqpTkVBflISsH
mean 20.05/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 76.04518s (SD = 47.293909s)
  • agent: uhCAkW2yo7q4tMwBZn0xS1BvaGWBpPFmD9lk5rARQeYP-uzs9wGXg
mean 50.636432s (SD = 36.121537s)
  • agent: uhCAkhanj90tY5zZa4Pn5ZtXU6pULuiohrGiFAbi__doXRZ-t_7ib
mean 41.841576s (SD = 36.473855s)
  • agent: uhCAkuVEJLz5Zsxzj9Upx5Uv2TUuzIoFcM7c86hozt2GJq4K3l_IK
mean 107.828682s (SD = 58.803179s)
  • agent: uhCAkyWw5H3J-hc5khrYAK-PFkXUXHbiyeN6lXb3kQmMWH_luLDLb
mean 103.874028s (SD = 57.777066s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 243.55/s
  • agent: uhCAkW2yo7q4tMwBZn0xS1BvaGWBpPFmD9lk5rARQeYP-uzs9wGXg
mean 115.6/s
  • agent: uhCAkhanj90tY5zZa4Pn5ZtXU6pULuiohrGiFAbi__doXRZ-t_7ib
mean 143.73/s
  • agent: uhCAkuVEJLz5Zsxzj9Upx5Uv2TUuzIoFcM7c86hozt2GJq4K3l_IK
mean 601/s
Not enough time data to show a trend.
  • agent: uhCAkyWw5H3J-hc5khrYAK-PFkXUXHbiyeN6lXb3kQmMWH_luLDLb
mean 113.88/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 4.05 (SD = 1.88) < max 9
zero-arc
min 0 < mean 5.43 (SD = 2.01) < max 9
Error count
The number of errors accumulated across all nodes.
2

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
Mon, 22 Dec 2025 20:57:31 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_20442873999
Call timing
The time taken for the call to complete.
mean 0.003322s (SD = 0.001628s)
Call rate
The number of zome calls completed per second.
mean 2986.38/s
Error count
The number of errors accumulated during the run.
0