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
Wed, 07 Jan 2026 14:29:40 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_20784185523
First install time
The time from conductor startup to completion of the first app installation attempt.
1.714900297s
Install app timing
The time taken to install an app.
mean 0.558903s (SD = 0.4339s)

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
Wed, 07 Jan 2026 14:31:57 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_20784185523
First install time
The time from conductor startup to completion of the first app installation attempt.
0.885260078s
Install app timing
The time taken to install an app.
mean 0.845626s (SD = 0.571405s)

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
Wed, 07 Jan 2026 14:34: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_20784185523
Create rate
The average number of created records per agent.
All agents
mean 78.71/s
  • agent: uhCAk9Nwvjn5yos31n0pZluEFdOz2oUt-xaU9a0NSyYG1SiaK0GSF
mean 117.46/s
  • agent: uhCAkDd7VXKCYLkavSIFeBvlfWQYY7ILWXzs3rNcDckBoGZRJXMuW
mean 27.22/s
  • agent: uhCAkFghQOmIE7nuRhVwlstZT1O5V01yb_7_HxoHN3-pW3DBV1-NN
mean 141.57/s
  • agent: uhCAkZgmqkinpHgoTxzzvc2cMVhQ4kWLzhaZmjSY5djdArI6xkwX-
mean 31.32/s
  • agent: uhCAkfLeGWtEB4mZsoA2b9h3ELcE2RsWixdZq7I0pL26VvrD39b4H
mean 75.96/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 5.405527182858657e+30s (SD = 1.8402755030785458e+31s)
  • agent: uhCAk5P2AtdhRCzCVK2xrrE9iGtge8BpehX3yq3ek59SXwy5Yd7oR
mean 155.140134s (SD = 66.484524s)
  • agent: uhCAk8DAuDu_WernmwfZ5cW3UF1EHizjyETa-R9O_ICV3tigyVwny
mean 89.236356s (SD = 29.618363s)
  • agent: uhCAkNciXYJm390rt5buAaXY6fU7q7pcdBHGzMtP3gn6kqcR2bXrv
mean 33.65769s (SD = 12.246487s)
  • agent: uhCAkdwF_Bz3WK7jCaspp7YiUGGRvyRAvVxuBRJ0-gIbmRCip7SSQ
mean 26.603606s (SD = 14.462604s)
  • agent: uhCAkidaoayf61a4tq96mDJexr-gGjC5bjkdre9KwUNwxYl8qvAed
mean 2.7027635914293286e+31s (SD = 9.20137751539273e+31s)
Sync lag rate
The average number of created records discovered per agent.
All agents
mean 217.89/s
  • agent: uhCAk5P2AtdhRCzCVK2xrrE9iGtge8BpehX3yq3ek59SXwy5Yd7oR
mean 70.44/s
  • agent: uhCAk8DAuDu_WernmwfZ5cW3UF1EHizjyETa-R9O_ICV3tigyVwny
mean 59.7/s
  • agent: uhCAkNciXYJm390rt5buAaXY6fU7q7pcdBHGzMtP3gn6kqcR2bXrv
mean 499/s
Not enough time data to show a trend.
  • agent: uhCAkdwF_Bz3WK7jCaspp7YiUGGRvyRAvVxuBRJ0-gIbmRCip7SSQ
mean 389/s
  • agent: uhCAkidaoayf61a4tq96mDJexr-gGjC5bjkdre9KwUNwxYl8qvAed
mean 71.33/s
Error count
The number of errors encountered during the scenario.
6

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
Wed, 07 Jan 2026 14:09:22 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_20784185523
Zome call timing
The time elapsed between start of install and calling init.
mean 0.020714s (SD = 0.008115s)

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
Wed, 07 Jan 2026 14:11:38 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_20784185523
Send timing
The time taken to emit a batch of 10,000 signals.
mean 1.070168s (SD = 0.557486s)
Not enough time data to show a trend.
Receive timing
The time taken to receive the completed batch, to the nearest 250ms.
mean 31.071319s (SD = 0.557664s)
Not enough time data to show a trend.
Success ratio
The proportion of signals successfully received in a batch.
min 0.6848999857902527 < mean 0.8514 (SD = 0.0766) < max 0.954200029373169

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
Wed, 07 Jan 2026 14:14:02 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_20784185523
Dispatch timing
The time between sending a remote call and the remote handler being invoked.
All agents
mean 0.00483s (SD = 0.024122s)
  • agent: uhCAkCqjqh1QOfnp-33xGtmRszdpB0k7yMcTHxzgIzNYZLou4tcSu
mean 0.005188s (SD = 0.030897s)
  • agent: uhCAkgpeN0cwiNTrYtY_A2Az_Y8KoGt5tVVPOdai-zN7uBAk9uvNq
mean 0.004472s (SD = 0.017346s)
Round-trip timing
The total elapsed time to get a response to the client.
All agents
mean 0.010541s (SD = 0.039654s)
  • agent: uhCAkCqjqh1QOfnp-33xGtmRszdpB0k7yMcTHxzgIzNYZLou4tcSu
mean 0.010541s (SD = 0.036002s)
  • agent: uhCAkgpeN0cwiNTrYtY_A2Az_Y8KoGt5tVVPOdai-zN7uBAk9uvNq
mean 0.01054s (SD = 0.043305s)

Remote Signals

This scenario tests the throughput of remote_signals operations.

Started
Wed, 07 Jan 2026 14:16: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_signals_20784185523
Round trip time
The time from origin signal dispatch to origin receive of the remote side's response signal.
mean 0.022077s (SD = 0.008364s)
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
Wed, 07 Jan 2026 14:18: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_20784185523
read call timing
The time it takes to complete the zome call that retrieves the record.
mean 0.005502s (SD = 0.001214s)
read call rate (10s)
The number of zome calls made in a 10-second window.
mean 1800.45/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
Wed, 07 Jan 2026 14:36:29 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_20784185523
Highest observed action_seq
The change in the highest action index on the write peer's source chain.
654 ⬆ 4205 change: 542.9663608562691% over 829.172315099s ( 4.28/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: uhCAkbo4g5cW73AwOqqk3QYSmc5cKFD4urh-n9VU4calZdS_n0Sj3
mean 0.049506s (SD = 0.077908s)
Error count
The number of errors accumulated.
1

Write/Query

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

Started
Wed, 07 Jan 2026 14:20: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_20784185523
Write timing
The time it takes to complete the zome function call that writes the entry.
mean 0.022627s (SD = 0.014758s)
Write rate
The number of writes completed per second.
mean 118.32/s
Error count
The number of errors accumulated during the run.
0

Write/Read

Creates an entry and reads it back, then repeats.

Started
Wed, 07 Jan 2026 14:23:03 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_20784185523
Write timing
The time taken to write the entry.
mean 0.02355s (SD = 0.00938s)
Write rate
The number of writes completed per second.
mean 161.82/s
Read timing
The time taken to read the entry.
mean 0.036472s (SD = 0.016886s)
Read rate
The number of reads completed per second.
mean 161.79/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
Wed, 07 Jan 2026 14:25:22 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_20784185523
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.223524s (SD = 0.516186s)
Write rate
The number of write zome function calls that complete per second.
mean 19.5/s
Read timing
The time it takes to complete the zome function call that reads the data.
mean 0.253864s (SD = 0.525703s)
Read rate
The number of read zome function calls that complete per second.
mean 19.5/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
Wed, 07 Jan 2026 14:38:49 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_20784185523
Highest observed action_seq
The change in the must_get_agent_activity peer's source chain top over the run.
16 ⬆ 1600 change: 9900% over 842.128277266s ( 1.88/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: uhCAkiKo5HC-f-EQpTzQGfBOif13rt-J_fmZEl6xJ1nJkmS_E775K
mean 0.045913s (SD = 0.019479s)
Error count
The number of errors accumulated over the run.
89046

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
Wed, 07 Jan 2026 14:48:34 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_20784185523
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 27.48/s
  • agent: uhCAkbgh3Yy-Ct6Iw0KNKRr9eE83k5GYfCvJWg8dYnZolezB8K7Oy
mean 38.92/s
  • agent: uhCAknPK-7bROKUh1HlWrl4SjdF77plAqhyD6XS0MV2UlYVUj0wfd
mean 16.04/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 3.402823669209384e+32s (SD = 6.474800354426833e+17s)
  • agent: uhCAkGlVJCiimGDL49YVNp-oZWt5WHO9XPYN34hAkHPXBfi-Goxiq
mean 3.4028236692093845e+32s (SD = 6.503492882861007e+17s)
  • agent: uhCAkniujGlUpGty2rkx9sjBMSCeq2vTSbs1UpctNmV92LIiTY1HW
mean 3.402823669209384e+32s (SD = 6.485183463413514e+17s)
  • agent: uhCAkrmIFfR6X3QIvhyrXoO6T0RU22aM5XBWUKTQdmGfbWalbRh1S
mean 3.402823669209383e+32s (SD = 6.435724717005978e+17s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 54.16/s
  • agent: uhCAkGlVJCiimGDL49YVNp-oZWt5WHO9XPYN34hAkHPXBfi-Goxiq
mean 47.09/s
  • agent: uhCAkniujGlUpGty2rkx9sjBMSCeq2vTSbs1UpctNmV92LIiTY1HW
mean 51.5/s
  • agent: uhCAkrmIFfR6X3QIvhyrXoO6T0RU22aM5XBWUKTQdmGfbWalbRh1S
mean 63.89/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 5.31 (SD = 1.8) < max 7
zero-arc
min 0 < mean 3.37 (SD = 0.89) < max 7
Error count
The number of errors accumulated across all nodes.
0

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
Wed, 07 Jan 2026 14:43:24 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_20784185523
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 55.45/s
  • agent: uhCAk9cqQFMnB2QXwTPGkfDxqF7DMkb-6bV0807peqYCXK5znGBAF
mean 35.35/s
  • agent: uhCAkOWRWu2R9eEanucwGagWENHAX8K6UsPaZFt1c3MtRSKcvSHvB
mean 37.8/s
  • agent: uhCAkac6f0z_FX6xRmCXM4MuJfVoAlBujqFd_M7VUKMFYuR0yxVly
mean 34.87/s
  • agent: uhCAkexVGLodSKHMA5CBQL8o3upIca6d8kh6Ess6UIQaykuM-Jvk1
mean 48.15/s
  • agent: uhCAkuXTEQ5chLD_7yc4tE3Vv4P9CwaABEOKWeF-Gd-zqWUqHdIG1
mean 21.87/s
  • agent: uhCAkvp_rfG34HXVaLxykNoC-X0jLZirxhGMNSI5KvfO3crPjBZw6
mean 154.64/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.4430854919384857e+32s (SD = 1.0421216014778741e+32s)
  • agent: uhCAk3jBxURJpeF05YXvQgCfQSQvav8xvez5EUJOi5m3Svk7uBrLb
mean 9.936031435996003e+31s (SD = 1.5471939399669854e+32s)
  • agent: uhCAkJV73HauDCVbXuktLKcR6ETtUv3sxdJolb5B09O-5sJrdmF9_
mean 176.7571s (SD = 67.658147s)
  • agent: uhCAkY14zUx7a1i6Ss3aGIYo7Ouw6aHRIe38tT1-9W15TKqK9VME9
mean 1.646594310450255e+32s (SD = 1.7005285266582483e+32s)
  • agent: uhCAkcO5vhaGEDSSuuv_MqSQfmqeT944WcalhjsJDJWyKiCJhXULB
mean 3.1321445137040874e+32s (SD = 9.20763939286263e+31s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 106.14/s
  • agent: uhCAk3jBxURJpeF05YXvQgCfQSQvav8xvez5EUJOi5m3Svk7uBrLb
mean 77.17/s
  • agent: uhCAkJV73HauDCVbXuktLKcR6ETtUv3sxdJolb5B09O-5sJrdmF9_
mean 85.8/s
  • agent: uhCAkY14zUx7a1i6Ss3aGIYo7Ouw6aHRIe38tT1-9W15TKqK9VME9
mean 207.6/s
  • agent: uhCAkcO5vhaGEDSSuuv_MqSQfmqeT944WcalhjsJDJWyKiCJhXULB
mean 54/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.06 (SD = 2.42) < max 9
zero-arc
min 1 < mean 6.65 (SD = 1.68) < 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
Wed, 07 Jan 2026 14:46:28 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_20784185523
Create rate
The number of timed entries created by the zero-arc node(s) per second.
All agents
mean 76.16/s
  • agent: uhCAk0GpLVJCL9gocgO4Zorulz37zD-nsH1_Bt3KJ0HJrRd4Kky9H
mean 132.29/s
  • agent: uhCAkBGnZpDG9GrrI4SPYZiSnGkJQlaToa2rao3ipcCkQ4S7zQqcY
mean 19.05/s
  • agent: uhCAkBqEO1PRgnwoUcopdsdjs1qwG-E4XXIKcpl-jfWrdDxAiSG59
mean 36.95/s
  • agent: uhCAkbHoDi_XmCPuZoLk3CZL46Nkkd9t0FnNG0AEBI5Id5CG8oFlF
mean 15/s
  • agent: uhCAkc9BMQvx03nJywaEGZrpoNFYVvekKfeHEVjupouivdF1F1x3H
mean 122.62/s
  • agent: uhCAkoV3Kg1ifQqiGHLA4qmpKgxVQsBu_OCb8GjDrIwFizKnXcg_M
mean 131.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 137.477242s (SD = 24.900656s)
  • agent: uhCAkR5307rYBorAG0PvrB7FzPc9mY5B6mPzTI8xUBqSdjnOnEOfB
mean 124.698628s (SD = 8.312241s)
Not enough time data to show a trend.
  • agent: uhCAkSJ1q4IOvr7Cj0zwkwbNGqbMQQO632vv_gsrk3JZBi642NI60
mean 258.502626s (SD = 25.359367s)
  • agent: uhCAkmd9MOnn-_xroid8bL3OWptsAdDrozUQm82X3sbOkeGqFXPsa
mean 125.901273s (SD = 52.501982s)
  • agent: uhCAkmqVpd5yJG8DhzSULnjqWdrPHwGCu8c5qGifQDJgHJkq_M8Jc
mean 40.806442s (SD = 13.429032s)
Sync lag rate
The number of entries per second received by full nodes.
All agents
mean 17.71/s
  • agent: uhCAkR5307rYBorAG0PvrB7FzPc9mY5B6mPzTI8xUBqSdjnOnEOfB
mean 0/s
Not enough time data to show a trend.
  • agent: uhCAkSJ1q4IOvr7Cj0zwkwbNGqbMQQO632vv_gsrk3JZBi642NI60
mean 8.5/s
  • agent: uhCAkmd9MOnn-_xroid8bL3OWptsAdDrozUQm82X3sbOkeGqFXPsa
mean 38/s
  • agent: uhCAkmqVpd5yJG8DhzSULnjqWdrPHwGCu8c5qGifQDJgHJkq_M8Jc
mean 24.33/s
Open connections
The number of currently open connections to other conductors.
full-arc
min 0 < mean 6.36 (SD = 2.78) < max 9
zero-arc
min 1 < mean 5.33 (SD = 1.89) < 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
Wed, 07 Jan 2026 14:27:26 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_20784185523
Call timing
The time taken for the call to complete.
mean 0.003064s (SD = 0.014775s)
Call rate
The number of zome calls completed per second.
mean 3235.45/s
Error count
The number of errors accumulated during the run.
0