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
Thu, 19 Mar 2026 01:07:20 UTC
Peer count
1
Peer count at end
1
Behaviours
  • large (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
app_install_large_23274364855
First install time
The time from conductor startup to completion of the first app installation attempt.
0.105217203s
Install app timing
The time taken to install an app.
mean 0.04476s (SD = 0.01832s) p50 0.043361s p95 0.049918s p99 0.057443s
Host Metrics
User CPU usage
CPU usage by user space
17.04%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 155.19 KiB/s < mean 167.78 KiB/s (SD = 6.72 KiB/s) < p95177.90 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 60.14 KiB/s < mean 73.63 KiB/s (SD = 35.87 KiB/s) < p95181.21 KiB/s
Total bytes received
Total bytes received on primary network interface
count
16.39 MiB
mean
167.78 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
7.19 MiB
mean
73.63 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 1375.46 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Warning Moderate swap usage (14.0% swap used)

System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 21.86% < mean 22.43% (SD = 0.37%) < p95 22.99%
System
5.39%
CPU percentiles
CPU usage percentiles
p50
22.56%
p95
22.99%
p99
22.99%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 40.04% < mean 53.62% (SD = 6.68%) < p95 60.29%
Memory available percentage
Percentage of available memory
p5 39.71% < mean 46.38% (SD = 6.68%) < p95 59.96%
Max host memory used
Maximum memory usage percentage across all hosts
max 53.62%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 13.98%
Memory growth rate
Rate of memory growth over time
growth 1375.46MB/s
Disk read throughput
Disk read throughput in MB/s
5.99MB/s
Disk write throughput
Disk write throughput in MB/s
52.72MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.12
5 min
0.72
15 min
0.49
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0.01% < mean 0.2918% (SD = 0.4424%) < p95 1.58%
60 second average
0.1900%
300 second average
0.0636%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0.07% < mean 0.2445% (SD = 0.1278%) < p95 0.47%
60 second average
0.1773%
300 second average
0.0536%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0.02% < mean 0.1864% (SD = 0.1425%) < p95 0.47%
60 second average
0.1427%
300 second average
0.0427%
Holochain process CPU usage
CPU usage by Holochain process
p5 16.9% < mean 17.63% (SD = 0.33%) < p95 17.96%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 23.41 KiB < mean 1.46 MiB (SD = 684.42 KiB) < p952.02 MiB
Holochain process threads
Number of threads in Holochain process
p5 12 threads < mean 20.83 threads (SD = 2.7 threads) < p95 22 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 8 file descriptors < mean 2059.17 file descriptors (SD = 1169.04 file descriptors) < p95 3135 file descriptors

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
Thu, 19 Mar 2026 01:09:12 UTC
Peer count
1
Peer count at end
1
Behaviours
  • minimal (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
app_install_minimal_23274364855
First install time
The time from conductor startup to completion of the first app installation attempt.
0.294786591s
Install app timing
The time taken to install an app.
mean 0.060599s (SD = 0.013971s) p50 0.059664s p95 0.07937s p99 0.122444s
Host Metrics
User CPU usage
CPU usage by user space
43.23%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 102.13 KiB/s < mean 1.32 MiB/s (SD = 1.25 MiB/s) < p952.51 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 29.01 KiB/s < mean 1.39 MiB/s (SD = 1.31 MiB/s) < p952.88 MiB/s
Total bytes received
Total bytes received on primary network interface
count
382.22 MiB
mean
1.32 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
402.21 MiB
mean
1.39 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 2209.70 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 17.83% < mean 51.63% (SD = 30.5%) < p95 83.12%
System
8.41%
CPU percentiles
CPU usage percentiles
p50
63.81%
p95
83.12%
p99
83.26%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
1 hosts
mean time
0.45s
Memory used percentage
Percentage of memory used
p5 9.83% < mean 19.14% (SD = 4.41%) < p95 23.04%
Memory available percentage
Percentage of available memory
p5 76.96% < mean 80.86% (SD = 4.41%) < p95 90.17%
Max host memory used
Maximum memory usage percentage across all hosts
max 19.14%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 9.88%
Memory growth rate
Rate of memory growth over time
growth 2209.70MB/s
Disk read throughput
Disk read throughput in MB/s
2.41MB/s
Disk write throughput
Disk write throughput in MB/s
52.69MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/1hosts
Mount Point /nix/store
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
3.81
5 min
1.47
15 min
0.55
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 8.7387% (SD = 8.9666%) < p95 21.31%
60 second average
6.2133%
300 second average
2.2047%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.048% (SD = 0.1165%) < p95 0.29%
60 second average
0.0380%
300 second average
0.0093%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0207% (SD = 0.0574%) < p95 0.14%
60 second average
0.0137%
300 second average
0.0007%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 1.2393% (SD = 1.1134%) < p95 3.54%
60 second average
0.9623%
300 second average
0.3807%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.4857% (SD = 0.6044%) < p95 1.67%
60 second average
0.4223%
300 second average
0.1813%
Holochain process CPU usage
CPU usage by Holochain process
p5 16.28% < mean 40.04% (SD = 22.06%) < p95 63.58%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 265.14 KiB < mean 853.23 KiB (SD = 642.69 KiB) < p952.01 MiB
Holochain process threads
Number of threads in Holochain process
p5 19 threads < mean 36.1 threads (SD = 15 threads) < p95 55 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 84 file descriptors < mean 967.67 file descriptors (SD = 1082.44 file descriptors) < p95 2651 file descriptors

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
Thu, 19 Mar 2026 01:11:29 UTC
Peer count
65
Peer count at end
65
Behaviours
  • record_lag (1 agent)
  • write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
dht_sync_lag_23274364855
Create rate
The average number of created records per agent.
Mean
mean 43.94/s
Max
Highest per-partition mean rate
max 96.21/s
Min
Lowest per-partition mean rate
min 12.9/s
Sync lag timing
The average time between when a record was created and when it is first seen by an agent.
Mean
mean 1.230652207630328e+31s (SD = 5.105933622711084e+31s)
Max
Highest per-partition mean latency
max mean 3.4778859560301794e+31s
Min
Lowest per-partition mean latency
min mean 380.878125s
Sync lag rate
The average number of created records discovered per agent.
Mean
mean 60.55/s
Max
Highest per-partition mean rate
max 171/s
Min
Lowest per-partition mean rate
min 0/s
Error count
The number of errors encountered during the scenario.
98
Host Metrics
User CPU usage
CPU usage by user space
40.43%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 119.94 KiB/s < mean 946.27 KiB/s (SD = 670.69 KiB/s) < p952.06 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 48.44 KiB/s < mean 919.56 KiB/s (SD = 974.27 KiB/s) < p952.91 MiB/s
Total bytes received
Total bytes received on primary network interface
count
97.13 GiB
mean
51.80 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
96.46 GiB
mean
51.45 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 95.2%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 527.46 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.3% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 33% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 15.54% < mean 48.05% (SD = 23.34%) < p95 90.63%
System
7.62%
CPU percentiles
CPU usage percentiles
p50
44.36%
p95
90.63%
p99
95.18%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
26 hosts
mean time
0.29s
Memory used percentage
Percentage of memory used
p5 8.68% < mean 21.01% (SD = 12.68%) < p95 47.72%
Memory available percentage
Percentage of available memory
p5 52.28% < mean 78.99% (SD = 12.68%) < p95 91.32%
Max host memory used
Maximum memory usage percentage across all hosts
max 68.55%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.31%
Memory growth rate
Rate of memory growth over time
growth 527.46MB/s
Disk read throughput
Disk read throughput in MB/s
1.37MB/s
Disk write throughput
Disk write throughput in MB/s
675.61MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/25hosts
Mount Point /boot
0/1hosts
Mount Point /efi-boot
0/19hosts
Mount Point /etc/hostname
0/34hosts
Mount Point /etc/hosts
0/34hosts
Mount Point /etc/resolv.conf
0/34hosts
Mount Point /nix/store
0/25hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
4.34
5 min
3.84
15 min
2.66
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
33.33%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 10.5761% (SD = 13.9452%) < p95 41.67%
60 second average
10.3998%
300 second average
9.3867%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0002% (SD = 0.008%) ≤ p95 0%
60 second average
0.0001%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0001% (SD = 0.0034%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 15.9726% (SD = 14.7504%) < p95 41.28%
60 second average
15.5756%
300 second average
13.4714%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 10.2598% (SD = 10.9788%) < p95 31.45%
60 second average
9.9541%
300 second average
8.5031%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 42.16% (SD = 23.48%) < p95 83.9%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 260.15 KiB < mean 511.74 KiB (SD = 138.39 KiB) < p95710.24 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 38.55 threads (SD = 13.4 threads) < p95 55 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 88.32 file descriptors (SD = 34.55 file descriptors) < p95 130 file descriptors

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
Thu, 19 Mar 2026 00:50:13 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
first_call_23274364855
Zome call timing
The time elapsed between start of install and calling init.
mean 0.023159s (SD = 0.064019s) p50 0.009639s p95 0.025025s p99 0.265254s
Host Metrics
User CPU usage
CPU usage by user space
9.77%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 96 B/s < mean 36.85 KiB/s (SD = 103.43 KiB/s) < p9546.30 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 260 B/s < mean 6.37 KiB/s (SD = 4.14 KiB/s) < p9512.92 KiB/s
Total bytes received
Total bytes received on primary network interface
count
10.80 MiB
mean
36.85 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
1.87 MiB
mean
6.37 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 1132.95 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 9.54% < mean 12.71% (SD = 6.12%) < p95 32.64%
System
2.94%
CPU percentiles
CPU usage percentiles
p50
11.20%
p95
32.64%
p99
37.73%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 15.57% < mean 22.97% (SD = 4.36%) < p95 27.4%
Memory available percentage
Percentage of available memory
p5 72.6% < mean 77.03% (SD = 4.36%) < p95 84.43%
Max host memory used
Maximum memory usage percentage across all hosts
max 22.97%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 1132.95MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
7.14MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/1hosts
Mount Point /efi-boot
0/1hosts
Mount Point /nix/store
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.68
5 min
0.79
15 min
0.32
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0.05% < mean 0.2494% (SD = 0.1353%) < p95 0.49%
60 second average
0.1932%
300 second average
0.0806%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 11.5% < mean 32.7606% (SD = 7.8378%) < p95 41.02%
60 second average
27.5316%
300 second average
13.1997%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 11.25% < mean 32.1974% (SD = 7.71%) < p95 40.09%
60 second average
27.0435%
300 second average
12.9639%
Holochain process CPU usage
CPU usage by Holochain process
p5 6.88% < mean 9.97% (SD = 4.34%) < p95 12.3%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 162.65 KiB < mean 856.86 KiB (SD = 351.09 KiB) < p951.17 MiB
Holochain process threads
Number of threads in Holochain process
p5 16 threads < mean 34.52 threads (SD = 9.55 threads) < p95 41 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 52 file descriptors < mean 398.65 file descriptors (SD = 211.34 file descriptors) < p95 613 file descriptors

Full-Arc Create (Validated) / Zero-Arc Read

A 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.
Started
Thu, 19 Mar 2026 04:43:12 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full (1 agent)
  • zero (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
full_arc_create_validated_zero_arc_read--high_zero_23274364855
Create rate
The number of timed entries created by the full-arc node(s) per second.
Mean
mean 31.24/s
Max
Highest per-partition mean rate
max 34.43/s
Min
Lowest per-partition mean rate
min 28.14/s
Fetch lag timing
For each entry, the time lag between when it was created by a full-arc node and when a zero-arc node fetched it from the network.
Mean
mean 134.094648s (SD = 110.458182s)
Max
Highest per-partition mean latency
max mean 1272.841132s
Min
Lowest per-partition mean latency
min mean 5.796327s
Fetch rate
The number of entries per second fetched by zero-arc nodes.
Mean
mean 155.36/s
Max
Highest per-partition mean rate
max 685/s
Min
Lowest per-partition mean rate
min 0/s
Open connections
The number of currently open connections to other conductors.
full-arc
p5 4 < mean 31.85 (SD = 19) < p95 60
zero-arc
p5 0 < mean 17.14 (SD = 14.26) < p95 38
Retrieval errors
Errors encountered by zero-arc nodes when attempting to retrieve entries created by full-arc nodes.
Total
578
Agents affected
56 / 58
Mean per agent
Total count divided by number of partitions, rounded to nearest whole number
10
Max
Highest count in any single partition
14
Min
Lowest count in any single partition
0
Error count
The number of errors accumulated across all nodes.
582

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
Thu, 19 Mar 2026 00:51:56 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
local_signals_23274364855
Send timing
The time taken to emit a batch of 10,000 signals.
mean 1.176281s (SD = 0.595202s) p50 1.330087s p95 2.019061s p99 2.019061s
Receive timing
The time taken to receive the completed batch, to the nearest 250ms.
mean 27.942265s (SD = 6.176448s) p50 30.001173s p95 30.001532s p99 30.001532s
Success ratio
The proportion of signals successfully received in a batch.
min 0.7336000204086304 < mean 0.8444 (SD = 0.0803) < max 0.933899998664856
Host Metrics
User CPU usage
CPU usage by user space
2.72%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 121 B/s < mean 19.09 KiB/s (SD = 101.16 KiB/s) ≤ p95950 B/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 17 B/s < mean 720 B/s (SD = 2.68 KiB/s) < p95759 B/s
Total bytes received
Total bytes received on primary network interface
count
5.59 MiB
mean
19.09 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
210.90 KiB
mean
720 B/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 141.76 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 1.3% < mean 5.65% (SD = 7.84%) < p95 14.25%
System
2.93%
CPU percentiles
CPU usage percentiles
p50
1.53%
p95
14.25%
p99
40.97%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 25.83% < mean 27.61% (SD = 0.83%) < p95 28.31%
Memory available percentage
Percentage of available memory
p5 71.69% < mean 72.39% (SD = 0.83%) < p95 74.17%
Max host memory used
Maximum memory usage percentage across all hosts
max 27.61%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 141.76MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
0.77MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
0.77
5 min
0.40
15 min
0.17
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0.12% < mean 1.5103% (SD = 1.5955%) < p95 5.64%
60 second average
1.1410%
300 second average
0.4684%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0.89% < mean 2.2616% (SD = 1.9425%) < p95 7.01%
60 second average
1.8310%
300 second average
0.9832%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0.86% < mean 2.2035% (SD = 1.9356%) < p95 6.86%
60 second average
1.7919%
300 second average
0.9661%
Holochain process CPU usage
CPU usage by Holochain process
p5 0.12% < mean 0.45% (SD = 0.78%) < p95 0.8%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 245.50 KiB ≤ mean 245.24 KiB (SD = 16.07 KiB) < p95250.16 KiB
Holochain process threads
Number of threads in Holochain process
p5 12 threads ≤ mean 11.77 threads (SD = 2.09 threads) < p95 12 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 47 file descriptors < mean 49.58 file descriptors (SD = 12.3 file descriptors) < p95 68 file descriptors

Mixed Arc get_agent_activity

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 calls get_agent_activity to observe new entries appearing on the writer's chain, measuring the lag between creation and discovery.
Started
Thu, 19 Mar 2026 04:59:36 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full_write (1 agent)
  • zero_read (1 agent)
  • zero_write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
mixed_arc_get_agent_activity_23274364855
Entry created count
The total number of entries created by write agents over the run, partitioned by agent and behaviour.
Total
390197
Agents affected
35 / 35
Mean per agent
Total count divided by number of partitions, rounded to nearest whole number
11148
Max
Highest count in any single partition
31420
Min
Lowest count in any single partition
899
Observed chain advancement
The maximum highest-observed action sequence per write agent, aggregated across all reading agents. The reading dimension is collapsed by taking the maximum observed value for each write agent (any reader successfully tracking that point counts as propagation). Captures how far readers tracked writers’ chains during the run.
Mean max (across write agents)
Mean of the highest chain head value observed per write agent. Each write agent contributes its maximum — the value seen by any reader.
7394.25
Max
Highest chain head value observed for any single write agent.
9580
Write agents observed
4
Chain head delay timing
The time lag between when a writer creates a new entry and when a reader discovers it via get_agent_activity. This is measured per new action in the chain.
Mean
mean 0.000827s (SD = 0.047683s)
Max
Highest per-partition mean latency
max mean 0.002988s
Min
Lowest per-partition mean latency
min mean -0.007806s
Chain head delay rate
The rate at which readers detect new chain heads appearing on writers' chains.
Mean
mean 40.66/s
Max
Highest per-partition mean rate
max 100.25/s
Min
Lowest per-partition mean rate
min 17.96/s
get_agent_activity_full zome call timing
The time taken to complete the get_agent_activity_full zome call that queries a writer's chain.
Mean
mean 0.162659s (SD = 0.161916s)
Max
Highest per-partition mean latency
max mean 0.306035s
Min
Lowest per-partition mean latency
min mean 0.006181s
Retrieval errors
A running accumulation of errors encountered by read agents when calling get_agent_activity.
Total
29
Agents affected
10 / 13
Mean per agent
Total count divided by number of partitions, rounded to nearest whole number
2
Max
Highest count in any single partition
5
Min
Lowest count in any single partition
0
Open connections
The number of currently open connections to other conductors, partitioned by agent behaviour.
  • behaviour: full_write
p5 17 < mean 39.51 (SD = 14.35) < p95 59
  • behaviour: zero_read
p5 0 < mean 32.33 (SD = 15.69) < p95 50
  • behaviour: zero_write
p5 23 < mean 38.95 (SD = 10.7) < p95 56
Final error count
The total number of errors accumulated across all agents over the run.
30
Host Metrics
User CPU usage
CPU usage by user space
21.93%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 3.53 KiB/s < mean 413.23 KiB/s (SD = 496.82 KiB/s) < p951.16 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 3.63 KiB/s < mean 371.69 KiB/s (SD = 606.45 KiB/s) < p951.62 MiB/s
Total bytes received
Total bytes received on primary network interface
count
19.14 GiB
mean
19.03 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
17.21 GiB
mean
17.11 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 96.5%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 430.79 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.2% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 7% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 1.22% < mean 27.12% (SD = 27.83%) < p95 91.58%
System
5.19%
CPU percentiles
CPU usage percentiles
p50
14.37%
p95
91.58%
p99
96.54%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
10 hosts
mean time
0.58s
Memory used percentage
Percentage of memory used
p5 7.23% < mean 18.17% (SD = 12.78%) < p95 47.2%
Memory available percentage
Percentage of available memory
p5 52.8% < mean 81.83% (SD = 12.78%) < p95 92.77%
Max host memory used
Maximum memory usage percentage across all hosts
max 67.94%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.16%
Memory growth rate
Rate of memory growth over time
growth 430.79MB/s
Disk read throughput
Disk read throughput in MB/s
1.22MB/s
Disk write throughput
Disk write throughput in MB/s
518.60MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/26hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/19hosts
Mount Point /etc/hostname
0/32hosts
Mount Point /etc/hosts
0/32hosts
Mount Point /etc/resolv.conf
0/32hosts
Mount Point /nix/store
0/26hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
2.36
5 min
1.86
15 min
1.46
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
6.78%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 6.7722% (SD = 16.1032%) < p95 43.35%
60 second average
6.3532%
300 second average
4.6745%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 10.5163% (SD = 15.0128%) < p95 43.85%
60 second average
10.0952%
300 second average
8.3795%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 9.0623% (SD = 13.7567%) < p95 42.19%
60 second average
8.7213%
300 second average
7.3463%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 22.7% (SD = 26.38%) < p95 89.62%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 220.29 KiB < mean 312.49 KiB (SD = 93.83 KiB) < p95507.46 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 24.59 threads (SD = 11.91 threads) < p95 41 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 69.46 file descriptors (SD = 27.18 file descriptors) < p95 112 file descriptors

Mixed Arc must_get_agent_activity

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.

Started
Thu, 19 Mar 2026 05:16:02 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full_write (1 agent)
  • zero_must_get_agent_activity (1 agent)
  • zero_write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
mixed_arc_must_get_agent_activity_23274364855
Highest observed action_seq
The maximum chain length observed per write 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.
Mean max (across write agents)
Mean of the highest chain head value observed per write agent. Each write agent contributes its maximum — the value seen by any reader.
1505.71
Max
Highest chain head value observed for any single write agent.
1743
Write agents observed
7
Chain batch delay timing
The time between a 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.
Mean
mean 69.806306s (SD = 38.5378s)
Max
Highest per-partition mean latency
max mean 271.537861s
Min
Lowest per-partition mean latency
min mean 13.699871s
Chain batch delay rate
The rate at which a must_get_agent_activity agent was able to discover batches and create/self-validate new entries that depend on them.
Mean
mean 2.14/s
Max
Highest per-partition mean rate
max 2.53/s
Min
Lowest per-partition mean rate
min 1.73/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.
Mean
mean 0.367683s (SD = 0.356313s)
Max
Highest per-partition mean latency
max mean 0.487717s
Min
Lowest per-partition mean latency
min mean 0.129876s
Retrieval errors
A running accumulation of the errors encountered by an agent when attempting to self-validate actions that depend on must_get_agent_activity calls.
Total
15803
Agents affected
15 / 15
Mean per agent
Total count divided by number of partitions, rounded to nearest whole number
1054
Max
Highest count in any single partition
1570
Min
Lowest count in any single partition
395
Open connections
The average number of open connections maintained by an agent over the run, broken down by behaviour.
  • behaviour: full_write
p5 34 < mean 51.71 (SD = 11.76) < p95 58
  • behaviour: zero_must_get_agent_activity
p5 21 < mean 36 (SD = 9.21) < p95 48
  • behaviour: zero_write
p5 20 < mean 36.76 (SD = 10.92) < p95 55
Final error count
The total number of all types of error accumulated over the run by all agents.
33208
Host Metrics
User CPU usage
CPU usage by user space
10.24%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 3.62 KiB/s < mean 176.30 KiB/s (SD = 285.56 KiB/s) < p95495.12 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 3.09 KiB/s < mean 158.31 KiB/s (SD = 220.69 KiB/s) < p95618.89 KiB/s
Total bytes received
Total bytes received on primary network interface
count
7.79 GiB
mean
8.40 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
7.00 GiB
mean
7.54 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 296.84 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.1% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 2% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 0.98% < mean 13.88% (SD = 16.72%) < p95 50.06%
System
3.64%
CPU percentiles
CPU usage percentiles
p50
5.21%
p95
50.06%
p99
73.49%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
6 hosts
mean time
0.04s
Memory used percentage
Percentage of memory used
p5 7.74% < mean 20.59% (SD = 13.12%) < p95 50.48%
Memory available percentage
Percentage of available memory
p5 49.52% < mean 79.41% (SD = 13.12%) < p95 92.26%
Max host memory used
Maximum memory usage percentage across all hosts
max 70.19%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.15%
Memory growth rate
Rate of memory growth over time
growth 296.84MB/s
Disk read throughput
Disk read throughput in MB/s
0.02MB/s
Disk write throughput
Disk write throughput in MB/s
367.74MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/22hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/16hosts
Mount Point /etc/hostname
0/31hosts
Mount Point /etc/hosts
0/31hosts
Mount Point /etc/resolv.conf
0/31hosts
Mount Point /nix/store
0/22hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.26
5 min
1.49
15 min
1.63
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
1.85%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 1.9661% (SD = 5.828%) < p95 8.31%
60 second average
1.9536%
300 second average
2.8282%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 7.2788% (SD = 12.1349%) < p95 35.38%
60 second average
7.3242%
300 second average
8.2598%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 6.214% (SD = 10.3188%) < p95 30.39%
60 second average
6.2951%
300 second average
7.1766%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 10.41% (SD = 14.01%) < p95 36.26%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 467.87 KiB < mean 553.90 KiB (SD = 87.27 KiB) < p95714.95 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 28.42 threads (SD = 11.81 threads) < p95 45 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 86.61 file descriptors (SD = 32.63 file descriptors) < p95 127 file descriptors

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
Thu, 19 Mar 2026 00:53:49 UTC
Peer count
10
Peer count at end
10
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
remote_call_rate_23274364855
Dispatch timing
The time between sending a remote call and the remote handler being invoked.
Mean
mean 0.029527s (SD = 0.056097s)
Max
Highest per-partition mean latency
max mean 0.056682s
Min
Lowest per-partition mean latency
min mean 0.016937s
Round-trip timing
The total elapsed time to get a response to the client.
Mean
mean 0.058422s (SD = 0.065467s)
Max
Highest per-partition mean latency
max mean 0.115531s
Min
Lowest per-partition mean latency
min mean 0.04014s
Host Metrics
User CPU usage
CPU usage by user space
7.47%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 15.81 KiB/s < mean 99.32 KiB/s (SD = 613.94 KiB/s) ≤ p9545.91 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 13.18 KiB/s < mean 26.38 KiB/s (SD = 12.27 KiB/s) < p9550.10 KiB/s
Total bytes received
Total bytes received on primary network interface
count
867.07 MiB
mean
965.09 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
230.33 MiB
mean
256.36 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 799.69 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Warning Moderate swap usage (16.5% swap used)

System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 3.61% < mean 12.2% (SD = 10.81%) < p95 24.43%
System
4.73%
CPU percentiles
CPU usage percentiles
p50
8.30%
p95
24.43%
p99
65.73%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
3 hosts
mean time
0.02s
Memory used percentage
Percentage of memory used
p5 14.65% < mean 23.45% (SD = 9.61%) < p95 44.79%
Memory available percentage
Percentage of available memory
p5 55.21% < mean 76.55% (SD = 9.61%) < p95 85.35%
Max host memory used
Maximum memory usage percentage across all hosts
max 44.72%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 16.46%
Memory growth rate
Rate of memory growth over time
growth 799.69MB/s
Disk read throughput
Disk read throughput in MB/s
0.30MB/s
Disk write throughput
Disk write throughput in MB/s
20.05MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/4hosts
Mount Point /efi-boot
0/4hosts
Mount Point /etc/hostname
0/6hosts
Mount Point /etc/hosts
0/6hosts
Mount Point /etc/resolv.conf
0/6hosts
Mount Point /nix/store
0/4hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
0.56
5 min
0.45
15 min
0.28
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 1.5984% (SD = 5.5169%) < p95 7.43%
60 second average
1.5867%
300 second average
1.2765%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 1.0257% (SD = 1.8414%) < p95 4.12%
60 second average
1.0334%
300 second average
0.9700%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.9566% (SD = 1.7451%) < p95 3.84%
60 second average
0.9659%
300 second average
0.9173%
Holochain process CPU usage
CPU usage by Holochain process
p5 0.68% < mean 4.87% (SD = 6.3%) < p95 17.72%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 168.66 KiB < mean 219.56 KiB (SD = 133.77 KiB) < p95247.51 KiB
Holochain process threads
Number of threads in Holochain process
p5 16 threads < mean 20.47 threads (SD = 4.76 threads) < p95 28 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 50 file descriptors < mean 75 file descriptors (SD = 199.52 file descriptors) < p95 88 file descriptors

Remote Signals

This scenario tests the throughput of remote_signals operations.

Started
Thu, 19 Mar 2026 00:55:56 UTC
Peer count
10
Peer count at end
10
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
remote_signals_23274364855
Round trip time
The time from origin signal dispatch to origin receive of the remote side's response signal.
mean 0.153769s (SD = 0.648963s) p50 0.096313s p95 0.25096s p99 0.281627s
Timeouts
The number of timeouts waiting for the remote side's response signal (default timeout is 20 seconds).
map[count:0 mean_rate_per_second:0 measurement_duration:map[nanos:119982993 secs:117] p5_rate_per_second:0 p95_rate_per_second:0 peak_rate_per_second:0 rate_trend:map[trend:[] window_duration:] std_rate_per_second:0]
Host Metrics
User CPU usage
CPU usage by user space
8.44%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 14.11 KiB/s < mean 59.23 KiB/s (SD = 371.41 KiB/s) ≤ p9546.44 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 13.88 KiB/s < mean 30.07 KiB/s (SD = 15.30 KiB/s) < p9551.10 KiB/s
Total bytes received
Total bytes received on primary network interface
count
259.70 MiB
mean
295.48 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
131.86 MiB
mean
150.02 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 8.23 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 2.5% < mean 13.79% (SD = 13.07%) < p95 24.55%
System
5.35%
CPU percentiles
CPU usage percentiles
p50
9.19%
p95
24.55%
p99
87.96%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
3 hosts
mean time
0.02s
Memory used percentage
Percentage of memory used
p5 16.57% < mean 21.64% (SD = 3.26%) < p95 27.45%
Memory available percentage
Percentage of available memory
p5 72.55% < mean 78.36% (SD = 3.26%) < p95 83.43%
Max host memory used
Maximum memory usage percentage across all hosts
max 27.31%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 5.16%
Memory growth rate
Rate of memory growth over time
growth 8.23MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
6.24MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/2hosts
Mount Point /efi-boot
0/2hosts
Mount Point /etc/hostname
0/3hosts
Mount Point /etc/hosts
0/3hosts
Mount Point /etc/resolv.conf
0/3hosts
Mount Point /nix/store
0/2hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
0.61
5 min
0.54
15 min
0.35
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 2.9821% (SD = 7.61%) < p95 8.29%
60 second average
3.0875%
300 second average
2.6953%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.7872% (SD = 1.7689%) < p95 3.67%
60 second average
0.7916%
300 second average
0.8476%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.7228% (SD = 1.6311%) < p95 3.44%
60 second average
0.7271%
300 second average
0.7913%
Holochain process CPU usage
CPU usage by Holochain process
p5 0.65% < mean 1.84% (SD = 4.64%) < p95 2.82%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 168.62 KiB < mean 192.00 KiB (SD = 27.48 KiB) < p95217.93 KiB
Holochain process threads
Number of threads in Holochain process
p5 16 threads < mean 21.74 threads (SD = 4.7 threads) < p95 28 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 49 file descriptors < mean 58.39 file descriptors (SD = 15.54 file descriptors) < p95 92 file descriptors

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
Thu, 19 Mar 2026 00:57:51 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
single_write_many_read_23274364855
read call timing
The time it takes to complete the zome call that retrieves the record.
mean 0.004003s (SD = 0.020529s) p50 0.00308s p95 0.003948s p99 0.007916s
read call rate
The number of read zome calls completed per second.
mean 2460.96/s
Error count
The number of errors collected.
0
Host Metrics
User CPU usage
CPU usage by user space
16.01%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 51 B/s < mean 288 B/s (SD = 635 B/s) < p95616 B/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 124 B/s < mean 886 B/s (SD = 851 B/s) < p951.84 KiB/s
Total bytes received
Total bytes received on primary network interface
count
81.46 KiB
mean
288 B/s
Total bytes sent
Total bytes sent on primary network interface
count
251.01 KiB
mean
886 B/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 33.96 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 18.22% < mean 23.47% (SD = 6.55%) < p95 24.62%
System
7.46%
CPU percentiles
CPU usage percentiles
p50
22.63%
p95
24.62%
p99
56.51%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 15.68% < mean 16.57% (SD = 0.5%) < p95 17.58%
Memory available percentage
Percentage of available memory
p5 82.42% < mean 83.43% (SD = 0.5%) < p95 84.32%
Max host memory used
Maximum memory usage percentage across all hosts
max 16.57%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 33.96MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
4.78MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/1hosts
Mount Point /efi-boot
0/1hosts
Mount Point /nix/store
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.13
5 min
1.03
15 min
0.64
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.012% (SD = 0.0364%) < p95 0.12%
60 second average
0.0123%
300 second average
0.0477%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 4.32% < mean 8.5287% (SD = 3.9039%) < p95 15.34%
60 second average
8.1267%
300 second average
12.5470%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 4.15% < mean 8.3503% (SD = 3.7893%) < p95 14.47%
60 second average
7.9493%
300 second average
12.3093%
Holochain process CPU usage
CPU usage by Holochain process
p5 15.5% < mean 20.42% (SD = 6.75%) < p95 21.28%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 204.27 KiB < mean 210.93 KiB (SD = 13.19 KiB) < p95214.09 KiB
Holochain process threads
Number of threads in Holochain process
p5 11 threads < mean 11.5 threads (SD = 0.81 threads) < p95 12 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 57 file descriptors < mean 58.37 file descriptors (SD = 7.83 file descriptors) < p95 68 file descriptors

Validation Receipts

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

Started
Thu, 19 Mar 2026 01:42:09 UTC
Peer count
20
Peer count at end
20
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
validation_receipts_23274364855
Receipts complete timing
The amount of time between publishing a record and receiving the required number of validation receipts.
Mean
mean 5.498972s (SD = 2.580619s)
Max
Highest per-partition mean latency
max mean 6.092773s
Min
Lowest per-partition mean latency
min mean 5.18682s
Receipts complete rate
The number of complete validation receipt sets collected per second.
Mean
mean 1.84/s
Max
Highest per-partition mean rate
max 1.94/s
Min
Lowest per-partition mean rate
min 1.75/s
Host Metrics
User CPU usage
CPU usage by user space
5.60%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 14.90 KiB/s < mean 51.92 KiB/s (SD = 302.25 KiB/s) < p9565.41 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 14.04 KiB/s < mean 30.72 KiB/s (SD = 22.84 KiB/s) < p9565.89 KiB/s
Total bytes received
Total bytes received on primary network interface
count
882.76 MiB
mean
961.64 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
522.23 MiB
mean
568.90 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 75.94 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (23.1% swap used)

System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 2.71% < mean 7.63% (SD = 7.4%) < p95 16.29%
System
2.03%
CPU percentiles
CPU usage percentiles
p50
5.90%
p95
16.29%
p99
39.55%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
4 hosts
mean time
0.01s
Memory used percentage
Percentage of memory used
p5 5.86% < mean 17.73% (SD = 9.38%) < p95 45.17%
Memory available percentage
Percentage of available memory
p5 54.84% < mean 82.27% (SD = 9.38%) < p95 94.14%
Max host memory used
Maximum memory usage percentage across all hosts
max 45.21%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 23.12%
Memory growth rate
Rate of memory growth over time
growth 75.94MB/s
Disk read throughput
Disk read throughput in MB/s
0.04MB/s
Disk write throughput
Disk write throughput in MB/s
57.17MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/8hosts
Mount Point /efi-boot
0/7hosts
Mount Point /etc/hostname
0/10hosts
Mount Point /etc/hosts
0/10hosts
Mount Point /etc/resolv.conf
0/10hosts
Mount Point /nix/store
0/8hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
0.92
5 min
1.84
15 min
2.77
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.6522% (SD = 3.1211%) < p95 3.34%
60 second average
1.3861%
300 second average
4.9742%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0.0005%) ≤ p95 0%
60 second average
0.0002%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 7.9969% (SD = 9.7263%) < p95 25.93%
60 second average
8.5679%
300 second average
10.6306%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 7.7316% (SD = 9.3525%) < p95 25.17%
60 second average
8.0771%
300 second average
8.8400%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 5% (SD = 5.06%) < p95 9.78%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 226.65 KiB < mean 252.77 KiB (SD = 42.97 KiB) < p95296.74 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 25.86 threads (SD = 7.83 threads) < p95 35 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 75.04 file descriptors (SD = 22.26 file descriptors) < p95 101 file descriptors

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
Thu, 19 Mar 2026 01:58:05 UTC
Peer count
65
Peer count at end
65
Behaviours
  • get_agent_activity (1 agent)
  • write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_get_agent_activity_23274364855
Observed chain advancement
The maximum highest-observed action sequence per write agent, aggregated across all reading agents. The reading dimension is collapsed by taking the maximum observed value for each write agent (any reader successfully tracking that point counts as propagation). Captures how far readers tracked writers’ chains during the run.
Mean max (across write agents)
Mean of the highest chain head value observed per write agent. Each write agent contributes its maximum — the value seen by any reader.
3069.82
Max
Highest chain head value observed for any single write agent.
7550
Write agents observed
11
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.
Mean
mean 0.16371s (SD = 0.280291s)
Max
Highest per-partition mean latency
max mean 0.317878s
Min
Lowest per-partition mean latency
min mean 0.013732s
Error count
The number of errors accumulated.
29
Host Metrics
User CPU usage
CPU usage by user space
35.12%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 11.28 KiB/s < mean 581.19 KiB/s (SD = 393.69 KiB/s) < p951.16 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 9.90 KiB/s < mean 496.34 KiB/s (SD = 370.20 KiB/s) < p951.06 MiB/s
Total bytes received
Total bytes received on primary network interface
count
22.70 GiB
mean
23.72 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
19.38 GiB
mean
20.25 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 96.4%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 734.12 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.3% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 5% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 6.13% < mean 42.16% (SD = 27.52%) < p95 93.14%
System
7.03%
CPU percentiles
CPU usage percentiles
p50
35.38%
p95
93.14%
p99
96.43%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
22 hosts
mean time
0.37s
Memory used percentage
Percentage of memory used
p5 6.86% < mean 20.86% (SD = 13.97%) < p95 48.96%
Memory available percentage
Percentage of available memory
p5 51.04% < mean 79.14% (SD = 13.97%) < p95 93.14%
Max host memory used
Maximum memory usage percentage across all hosts
max 67.88%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.27%
Memory growth rate
Rate of memory growth over time
growth 734.12MB/s
Disk read throughput
Disk read throughput in MB/s
42.40MB/s
Disk write throughput
Disk write throughput in MB/s
622.67MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/25hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/19hosts
Mount Point /etc/hostname
0/29hosts
Mount Point /etc/hosts
0/29hosts
Mount Point /etc/resolv.conf
0/29hosts
Mount Point /nix/store
0/25hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
3.45
5 min
2.52
15 min
2.15
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
5.45%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 6.4251% (SD = 10.3091%) < p95 26.39%
60 second average
5.9671%
300 second average
4.2898%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 13.8568% (SD = 13.7197%) < p95 35.6%
60 second average
13.0904%
300 second average
10.3372%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 10.1915% (SD = 10.6414%) < p95 27.97%
60 second average
9.6553%
300 second average
7.8494%
Holochain process CPU usage
CPU usage by Holochain process
p5 2.75% < mean 38.54% (SD = 26.56%) < p95 90.1%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 236.45 KiB < mean 368.80 KiB (SD = 87.88 KiB) < p95529.02 KiB
Holochain process threads
Number of threads in Holochain process
p5 13 threads < mean 33.37 threads (SD = 10.65 threads) < p95 50 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 56 file descriptors < mean 83.32 file descriptors (SD = 24.54 file descriptors) < p95 126 file descriptors

Write/get_agent_activity with volatile conductors

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.

Started
Thu, 19 Mar 2026 02:14:39 UTC
Peer count
65
Peer count at end
65
Behaviours
  • get_agent_activity_volatile (1 agent)
  • write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_get_agent_activity_volatile_23274364855
Highest observed action_seq
The rate at which zero-arc readers observe new chain heads on the writers' chains via get_agent_activity. This reflects the DHT's ability to propagate agent activity ops and make them available to querying peers.
Mean
mean 257.11/s
Max
Highest per-partition mean rate
max 1805.57/s
Min
Lowest per-partition mean rate
min 6.81/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.
Mean
mean 0.264448s (SD = 1.200597s)
Max
Highest per-partition mean latency
max mean 1.151708s
Min
Lowest per-partition mean latency
min mean 0.00366s
Running volatile conductors count
The number of conductors running by get_agent_activity_volatile peers.
p5 20 conductors < mean 24.3 conductors (SD = 2.95 conductors) < p95 28 conductors
Volatile conductor total running duration
The total running duration of a get_agent_activity_volatile conductor.
Mean
mean 665.529044s (SD = 412.794339s)
Max
Highest per-partition mean latency
max mean 863.818182s
Min
Lowest per-partition mean latency
min mean 495.4s
Volatile conductor running duration
The duration that a get_agent_activity_volatile conductor was running before being stopped.
Mean
mean 56.256199s (SD = 33.861379s)
Max
Highest per-partition mean latency
max mean 108.424123s
Min
Lowest per-partition mean latency
min mean 31.913042s
Volatile conductor stopped duration
The duration that a get_agent_activity_volatile conductor was stopped before being started again.
Mean
mean 53.076775s (SD = 37.782548s)
Max
Highest per-partition mean latency
max mean 79.064602s
Min
Lowest per-partition mean latency
min mean 26.137117s
Reached target arc
Did get_agent_activity_volatile peer reach their target arc in the moment before they were shutdown.
  • get_agent_activity_volatile_agent: uhCAk5H4rGTLzqBEwRVPqXwozWnxtuqagQMRc9m_v8KNp31-VuNlA
p5 0 < mean 0.04 (SD = 0.19) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAk9EOG-tQPXJxx8wT2QTHSldF944xjI5iVwhHHNCHKkko7bCsm
p5 0 < mean 0.04 (SD = 0.19) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkEk5xTv-I-thZPfi85PJb09owdpvpt_w3ddO6HC2DApTlo78a
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkF4Tb2MF6xJbBTrSrKFB4df9hWLdEv3h1iMuSixCXYt1rN5Zd
p5 0 < mean 0.04 (SD = 0.19) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkH-Ly7hHZQtzeoIALPZ9zCuIkieJCQOetUPDDlDTTqpr154UB
p5 0 < mean 0.04 (SD = 0.19) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkI2LgAfE89ctZbeCKKmebFa9yWeqPnbGNln6aigwTJjI706PG
p5 0 < mean 0.04 (SD = 0.2) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkJqw4X4YtNN6AzxMr_uUJ9DzsM_alcowU-xSxbuBbQbDWMUGY
p5 0 < mean 0.06 (SD = 0.23) < p95 1
  • get_agent_activity_volatile_agent: uhCAkKC_blY8vErfl_8PPc5Yxpu_dGx43LDnvtbjJTMlwjWuoM9l4
p5 0 < mean 0.05 (SD = 0.22) < p95 1
  • get_agent_activity_volatile_agent: uhCAkKuYfL674nBd5sNfRkkJc9NTjDUCAXopVjaShVE5qmGvoUQ3U
p5 0 < mean 0.04 (SD = 0.2) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkMHk-ykbk4KvuN3UF7rzwzojTD3snU5aTdhUpE0bksGaR1_EJ
p5 0 < mean 0.04 (SD = 0.19) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkNerbleqbfrdjKs3WZn5s35uLj4sC76BIa4G7KxJr3sOesSjo
p5 0 < mean 0.04 (SD = 0.2) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkSbp6DJX_vFt7sH7i8vgWN_dTMswxGZD7EhsXhsH-HGQsFTGM
p5 0 < mean 0.03 (SD = 0.18) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkSdBc_CtEQcC73u5q-TtFwJ5arxTWJlnaoygDSmHK3WK_xfjf
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkW815eiNMepjFwSPkxfTviS3nt5bTSUgWP8vT80RF66TG2Yym
p5 0 < mean 0.05 (SD = 0.21) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkbkEKFPDrMKYaEh1yU3jmJJRgKwNY_7F8mrMR6-0qhiwNTMBu
p5 0 < mean 0.06 (SD = 0.24) < p95 1
  • get_agent_activity_volatile_agent: uhCAkeb8LqD7VahABs9jXU-NPh7uU2zae69PwsTLUcLd4e1GbEMQ8
p5 0 < mean 0.05 (SD = 0.22) < p95 1
  • get_agent_activity_volatile_agent: uhCAkfxRYOmWn80GmseOkcxGqcmtmzx395amTlseJGEcXRoccYZlH
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkgX1E47ePGYNQKHN75EnpzpcRGHBYEJ6p481Sy6gUi1V-OhlT
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkidpeHP7pb4qm-4c2asQtCSYLy_sSn52igarYzD1KocJQFfmD
p5 0 < mean 0.05 (SD = 0.21) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkjQ4zKlFq4QYyyORihH4N2LD8t1rtNYzkC8k4gDawjAABQZzT
p5 0 < mean 0.05 (SD = 0.21) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkjQdPicjVJmThvvE0oulOs2-vMrLIhjuPfoXGjWo4YwyVYVXf
p5 0 < mean 0.03 (SD = 0.18) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkk_G7t_RMVavxmx1QKz-9Z9EwXNENTpBKg7NpkAf3fsWSO3D7
p5 0 < mean 0.03 (SD = 0.18) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkkmsLH5BJ6FEeX2H6QeWSAjFtUUhhQPvj1TWZfLqryFwlInO6
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkmwIbKr_xdpS6M5h7EFiwPA7AKxKJ-PIUQvzsjNZ-uqjjVyqo
p5 0 < mean 0.05 (SD = 0.21) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkna0mW6rVWXegquWrO9hRFll-WlfCxBcn_nHwUlJ_2U9NvsZi
p5 0 ≤ mean 0 (SD = 0) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkpP9hJ3xS5nYatGKY6zYorBbqSL3z5qj3DiHBqVJEMyU8cSv9
p5 0 < mean 0.04 (SD = 0.2) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkq1RkM0DMpC0m-wnJvZkSsmcToh8JQyubgIeXESh-gD_NW77H
p5 0 < mean 0.05 (SD = 0.21) ≤ p95 0
  • get_agent_activity_volatile_agent: uhCAkwPM8L_40TlJqUGiaFndxdLhm8paoiFOZxxnoEeFMzsiDrYnG
p5 0 < mean 0.06 (SD = 0.24) < p95 1
  • get_agent_activity_volatile_agent: uhCAkzH-BKze7Zn4RbIZHB-9PSNAzQiRHtI7beIYTcpBa_5ZcWMGA
p5 0 < mean 0.04 (SD = 0.2) ≤ p95 0
Error count
The number of errors accumulated.
731

Write/Query

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

Started
Thu, 19 Mar 2026 00:59:48 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_query_23274364855
Write timing
The time it takes to complete the zome function call that writes the entry.
mean 0.009979s (SD = 0.004184s) p50 0.008525s p95 0.0196s p99 0.02493s
Write rate
The number of writes completed per second.
mean 147.82/s
Query timing
The time it takes to complete the chain_query_count_len zome call that queries the source chain.
mean 0.053304s (SD = 0.033197s) p50 0.048862s p95 0.109919s p99 0.12159s
Query rate
The number of chain queries completed per second.
mean 147.82/s
Error count
The number of errors accumulated during the run.
0
Host Metrics
User CPU usage
CPU usage by user space
17.66%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 19.79 KiB/s < mean 23.22 KiB/s (SD = 2.38 KiB/s) < p9528.22 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 19.11 KiB/s < mean 26.57 KiB/s (SD = 11.09 KiB/s) < p9549.65 KiB/s
Total bytes received
Total bytes received on primary network interface
count
6.58 MiB
mean
23.22 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
7.52 MiB
mean
26.57 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 12.19 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Warning Moderate swap usage (16.5% swap used)

System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 23.06% < mean 24.51% (SD = 2.47%) < p95 24.84%
System
6.85%
CPU percentiles
CPU usage percentiles
p50
24.12%
p95
24.84%
p99
37.35%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 33.08% < mean 33.4% (SD = 0.22%) < p95 33.79%
Memory available percentage
Percentage of available memory
p5 66.21% < mean 66.6% (SD = 0.22%) < p95 66.92%
Max host memory used
Maximum memory usage percentage across all hosts
max 33.40%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 16.46%
Memory growth rate
Rate of memory growth over time
growth 12.19MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
13.98MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.59
5 min
0.98
15 min
0.57
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0533% (SD = 0.1949%) < p95 0.38%
60 second average
0.0560%
300 second average
0.0280%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.0077% (SD = 0.0299%) < p95 0.05%
60 second average
0.0073%
300 second average
0.0003%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.0033% (SD = 0.0147%) < p95 0.02%
60 second average
0.0023%
300 second average
0.0000%
Holochain process CPU usage
CPU usage by Holochain process
p5 17.44% < mean 18.86% (SD = 2.42%) < p95 19.08%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 235.06 KiB < mean 243.24 KiB (SD = 40.86 KiB) < p95262.37 KiB
Holochain process threads
Number of threads in Holochain process
p5 16 threads < mean 16.77 threads (SD = 1.09 threads) < p95 17 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 58 file descriptors < mean 58.9 file descriptors (SD = 9.25 file descriptors) < p95 66 file descriptors

Write/Read

Creates an entry and reads it back, then repeats.

Started
Thu, 19 Mar 2026 01:01:52 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_read_23274364855
Write timing
The time taken to write the entry.
mean 0.025011s (SD = 0.01716s) p50 0.023732s p95 0.043201s p99 0.060185s
Write rate
The number of writes completed per second.
mean 171.38/s
Read timing
The time taken to read the entry.
mean 0.032762s (SD = 0.020725s) p50 0.02697s p95 0.068881s p99 0.07381s
Read rate
The number of reads completed per second.
mean 171.38/s
Error count
The number of errors accumulated over the run.
0
Host Metrics
User CPU usage
CPU usage by user space
12.78%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 760 B/s < mean 47.03 KiB/s (SD = 247.95 KiB/s) ≤ p952.13 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 1.69 KiB/s < mean 3.52 KiB/s (SD = 7.79 KiB/s) < p953.63 KiB/s
Total bytes received
Total bytes received on primary network interface
count
13.78 MiB
mean
47.03 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
1.03 MiB
mean
3.52 KiB/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 25.17 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 13.52% < mean 16.51% (SD = 2.24%) < p95 17.43%
System
3.73%
CPU percentiles
CPU usage percentiles
p50
16.69%
p95
17.43%
p99
26.57%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 16.8% < mean 16.91% (SD = 0.58%) < p95 17.18%
Memory available percentage
Percentage of available memory
p5 82.82% < mean 83.09% (SD = 0.58%) < p95 83.2%
Max host memory used
Maximum memory usage percentage across all hosts
max 16.91%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 25.17MB/s
Disk read throughput
Disk read throughput in MB/s
0.02MB/s
Disk write throughput
Disk write throughput in MB/s
7.05MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.38
5 min
0.64
15 min
0.26
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0503% (SD = 0.1551%) < p95 0.61%
60 second average
0.0381%
300 second average
0.0123%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.3577% (SD = 0.6495%) < p95 1.87%
60 second average
0.2774%
300 second average
0.1174%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 0.3435% (SD = 0.6221%) < p95 1.87%
60 second average
0.2684%
300 second average
0.1135%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 250.98 KiB < mean 263.89 KiB (SD = 5.46 KiB) < p95270.09 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads ≤ mean 1 threads (SD = 0 threads) ≤ p95 1 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors ≤ mean 0 file descriptors (SD = 0 file descriptors) ≤ p95 0 file descriptors

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
Thu, 19 Mar 2026 01:03:45 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_validated_23274364855
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.091135s (SD = 0.202224s) p50 0.068792s p95 0.139292s p99 0.461933s
Write rate
The number of write zome function calls that complete per second.
mean 41.96/s
Read timing
The time it takes to complete the zome function call that reads the data.
mean 0.147643s (SD = 0.329305s) p50 0.115889s p95 0.201977s p99 0.570375s
Read rate
The number of read zome function calls that complete per second.
mean 40/s
Error count
The number of errors accumulated over the run.
0
Host Metrics
User CPU usage
CPU usage by user space
15.65%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 352 B/s < mean 675 B/s (SD = 484 B/s) < p951.15 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 17 B/s < mean 250 B/s (SD = 371 B/s) < p95780 B/s
Total bytes received
Total bytes received on primary network interface
count
191.20 KiB
mean
675 B/s
Total bytes sent
Total bytes sent on primary network interface
count
70.78 KiB
mean
250 B/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 32.83 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 6.01% < mean 21.03% (SD = 8.26%) < p95 29.41%
System
5.38%
CPU percentiles
CPU usage percentiles
p50
23.37%
p95
29.41%
p99
44.04%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 67.77% < mean 68.71% (SD = 0.35%) < p95 69.19%
Memory available percentage
Percentage of available memory
p5 30.81% < mean 31.29% (SD = 0.35%) < p95 32.23%
Max host memory used
Maximum memory usage percentage across all hosts
max 68.71%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 32.83MB/s
Disk read throughput
Disk read throughput in MB/s
0.02MB/s
Disk write throughput
Disk write throughput in MB/s
15.94MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
2.34
5 min
1.21
15 min
0.56
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0.95% < mean 4.75% (SD = 2.3602%) < p95 7.8%
60 second average
3.9373%
300 second average
1.8797%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 11.2643% (SD = 18.9915%) < p95 50.09%
60 second average
9.6823%
300 second average
3.9837%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 10.851% (SD = 18.3365%) < p95 48.46%
60 second average
9.3263%
300 second average
3.8300%
Holochain process CPU usage
CPU usage by Holochain process
p5 4.94% < mean 19.62% (SD = 8.14%) < p95 28.01%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 144.96 KiB < mean 417.11 KiB (SD = 92.89 KiB) < p95443.69 KiB
Holochain process threads
Number of threads in Holochain process
p5 12 threads < mean 15.27 threads (SD = 1.9 threads) < p95 16 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 38 file descriptors < mean 61.53 file descriptors (SD = 10.67 file descriptors) < p95 68 file descriptors

Write Validated must_get_agent_activity

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.

Started
Thu, 19 Mar 2026 02:46:05 UTC
Peer count
65
Peer count at end
65
Behaviours
  • must_get_agent_activity (1 agent)
  • write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
write_validated_must_get_agent_activity_23274364855
Highest observed action_seq
The maximum chain length observed per write 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.
Mean max (across write agents)
Mean of the highest chain head value observed per write agent. Each write agent contributes its maximum — the value seen by any reader.
849.46
Max
Highest chain head value observed for any single write agent.
1754
Write agents observed
13
Chain batch delay timing
The time between a 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.
Mean
mean 259.674475s (SD = 53.386798s)
Max
Highest per-partition mean latency
max mean 1502.019s
Min
Lowest per-partition mean latency
min mean -73.376174s
Chain batch delay rate
The rate at which a must_get_agent_activity agent was able to discover batches and create/self-validate new entries that depend on them.
Mean
mean 3.03/s
Max
Highest per-partition mean rate
max 7.2/s
Min
Lowest per-partition mean rate
min 0/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.
Mean
mean 0.581619s (SD = 0.242768s)
Max
Highest per-partition mean latency
max mean 4.435473s
Min
Lowest per-partition mean latency
min mean 0.105449s
Retrieval errors
A running accumulation of the errors encountered by an agent when attempting to self-validate actions that depend on must_get_agent_activity calls.
Total
13170
Agents affected
32 / 33
Mean per agent
Total count divided by number of partitions, rounded to nearest whole number
399
Max
Highest count in any single partition
795
Min
Lowest count in any single partition
0
Final error count
The total number of all types of error accumulated over the run by all agents.
105903
Host Metrics
User CPU usage
CPU usage by user space
19.77%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 61.85 KiB/s < mean 193.03 KiB/s (SD = 269.88 KiB/s) < p95344.46 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 28.77 KiB/s < mean 167.63 KiB/s (SD = 157.43 KiB/s) < p95474.75 KiB/s
Total bytes received
Total bytes received on primary network interface
count
10.40 GiB
mean
10.87 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
9.03 GiB
mean
9.44 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 92.4%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 526.54 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.3% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 2% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 6.64% < mean 25.36% (SD = 18.75%) < p95 67.04%
System
5.59%
CPU percentiles
CPU usage percentiles
p50
19.63%
p95
67.04%
p99
92.41%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
10 hosts
mean time
0.17s
Memory used percentage
Percentage of memory used
p5 8.65% < mean 21.55% (SD = 12.83%) < p95 50.16%
Memory available percentage
Percentage of available memory
p5 49.84% < mean 78.45% (SD = 12.83%) < p95 91.35%
Max host memory used
Maximum memory usage percentage across all hosts
max 69.91%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.34%
Memory growth rate
Rate of memory growth over time
growth 526.54MB/s
Disk read throughput
Disk read throughput in MB/s
0.74MB/s
Disk write throughput
Disk write throughput in MB/s
843.59MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/27hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/20hosts
Mount Point /etc/hostname
0/34hosts
Mount Point /etc/hosts
0/34hosts
Mount Point /etc/resolv.conf
0/34hosts
Mount Point /nix/store
0/27hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
2.32
5 min
1.85
15 min
1.46
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
1.61%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 3.1804% (SD = 8.3633%) < p95 14.92%
60 second average
3.0231%
300 second average
2.4098%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 16.6795% (SD = 15.2694%) < p95 40.69%
60 second average
16.0061%
300 second average
12.8984%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 14.884% (SD = 13.6883%) < p95 36.45%
60 second average
14.3411%
300 second average
11.6906%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 21.2% (SD = 16.84%) < p95 57.43%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 469.79 KiB < mean 579.49 KiB (SD = 88.84 KiB) < p95704.75 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 37.65 threads (SD = 13.75 threads) < p95 59 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 91.81 file descriptors (SD = 29.7 file descriptors) < p95 126 file descriptors

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
Thu, 19 Mar 2026 04:08:13 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full (1 agent)
  • zero_read (1 agent)
  • zero_write (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
zero_arc_create_and_read_23274364855
Create rate
The number of timed entries created by the zero-arc write node(s) per second.
Mean
mean 78.64/s
Max
Highest per-partition mean rate
max 134.92/s
Min
Lowest per-partition mean rate
min 28.25/s
Fetch lag timing
For each entry, the time lag between when it was created and when a zero-arc read node fetched it from the network via the get_timed_entries_network zome function.
Mean
mean 218.11567s (SD = 28.781282s)
Max
Highest per-partition mean latency
max mean 1308.126514s
Min
Lowest per-partition mean latency
min mean 96.405122s
Fetch lag rate
The number of entries per second fetched by zero-arc read nodes.
Mean
mean 5.42/s
Max
Highest per-partition mean rate
max 16/s
Min
Lowest per-partition mean rate
min 0/s
Open connections
The number of currently open connections to other conductors.
full-arc
p5 28 < mean 45.4 (SD = 12.94) < p95 58
zero-arc
p5 7 < mean 28.06 (SD = 9.81) < p95 40
Error count
The number of errors accumulated across all nodes.
218

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
Thu, 19 Mar 2026 03:19:06 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full (1 agent)
  • zero (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
zero_arc_create_data--high_zero_23274364855
Create rate
The number of timed entries created by the zero-arc node(s) per second.
Mean
mean 67.81/s
Max
Highest per-partition mean rate
max 140.97/s
Min
Lowest per-partition mean rate
min 18.01/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.
Mean
mean 559.830901s (SD = 149.613449s)
Max
Highest per-partition mean latency
max mean 673.968507s
Min
Lowest per-partition mean latency
min mean 345.901541s
Sync lag rate
The number of entries per second received by full nodes.
Mean
mean 8.16/s
Max
Highest per-partition mean rate
max 18.8/s
Min
Lowest per-partition mean rate
min 1.67/s
Open connections
The number of currently open connections to other conductors.
full-arc
p5 22 < mean 46.07 (SD = 10.84) < p95 56
zero-arc
p5 11 < mean 34.65 (SD = 11.48) < p95 48
Error count
The number of errors accumulated across all nodes.
4
Host Metrics
User CPU usage
CPU usage by user space
21.07%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 4.23 KiB/s < mean 169.50 KiB/s (SD = 486.78 KiB/s) < p951.09 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 3.70 KiB/s < mean 139.98 KiB/s (SD = 186.14 KiB/s) < p95522.56 KiB/s
Total bytes received
Total bytes received on primary network interface
count
8.14 GiB
mean
8.69 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
6.72 GiB
mean
7.17 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 92.6%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 365.34 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.3% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 7% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 2.65% < mean 25.1% (SD = 21.23%) < p95 66.7%
System
4.02%
CPU percentiles
CPU usage percentiles
p50
19.94%
p95
66.70%
p99
92.60%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
3 hosts
mean time
0.39s
Memory used percentage
Percentage of memory used
p5 7.14% < mean 18.32% (SD = 11.96%) < p95 46.26%
Memory available percentage
Percentage of available memory
p5 53.74% < mean 81.68% (SD = 11.96%) < p95 92.86%
Max host memory used
Maximum memory usage percentage across all hosts
max 65.51%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.30%
Memory growth rate
Rate of memory growth over time
growth 365.34MB/s
Disk read throughput
Disk read throughput in MB/s
0.56MB/s
Disk write throughput
Disk write throughput in MB/s
797.96MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/25hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/19hosts
Mount Point /etc/hostname
0/33hosts
Mount Point /etc/hosts
0/33hosts
Mount Point /etc/resolv.conf
0/33hosts
Mount Point /nix/store
0/25hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
2.43
5 min
2.46
15 min
2.37
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
6.78%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 3.5013% (SD = 8.3093%) < p95 18.97%
60 second average
3.4324%
300 second average
3.7290%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 19.7978% (SD = 19.7939%) < p95 51.73%
60 second average
19.4262%
300 second average
18.9834%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 18.7269% (SD = 19.3355%) < p95 50.18%
60 second average
18.3755%
300 second average
17.8781%
Holochain process CPU usage
CPU usage by Holochain process
p5 0.17% < mean 22.23% (SD = 20.46%) < p95 62.38%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 235.12 KiB < mean 317.33 KiB (SD = 64.86 KiB) < p95412.62 KiB
Holochain process threads
Number of threads in Holochain process
p5 11 threads < mean 32.15 threads (SD = 11.79 threads) < p95 46 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 44 file descriptors < mean 82.69 file descriptors (SD = 26.97 file descriptors) < p95 121 file descriptors

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
Thu, 19 Mar 2026 03:51:54 UTC
Peer count
65
Peer count at end
65
Behaviours
  • full (1 agent)
  • zero (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
zero_arc_create_data_validated--high_zero_23274364855
Create rate
The number of timed entries created by the zero-arc node(s) per second.
Mean
mean 60.74/s
Max
Highest per-partition mean rate
max 137.05/s
Min
Lowest per-partition mean rate
min 23.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.
Mean
mean 312.828303s (SD = 132.828922s)
Max
Highest per-partition mean latency
max mean 384.170119s
Min
Lowest per-partition mean latency
min mean 193.620449s
Sync lag rate
The number of entries per second received by full nodes.
Mean
mean 72.63/s
Max
Highest per-partition mean rate
max 190/s
Min
Lowest per-partition mean rate
min 0/s
Open connections
The number of currently open connections to other conductors.
full-arc
p5 31 < mean 43.64 (SD = 12.34) < p95 58
zero-arc
p5 5 < mean 28.25 (SD = 12.31) < p95 43
Error count
The number of errors accumulated across all nodes.
9
Host Metrics
User CPU usage
CPU usage by user space
23.96%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 2.17 KiB/s < mean 179.66 KiB/s (SD = 540.83 KiB/s) < p951.04 MiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 1.62 KiB/s < mean 156.85 KiB/s (SD = 239.24 KiB/s) < p95527.58 KiB/s
Total bytes received
Total bytes received on primary network interface
count
8.52 GiB
mean
9.09 MiB/s
Total bytes sent
Total bytes sent on primary network interface
count
7.44 GiB
mean
7.94 MiB/s
CPU spike anomaly
CPU spike anomaly was detected
Detected

Warning CPU p99 reached 95.0%

Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 572.09 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
Detected

Critical Heavy swap usage (39.3% swap used)

System overload anomaly
System overload anomaly was detected
Detected

Warning 5% of hosts overloaded (load5/ncpus > 1.0)

Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 3.47% < mean 30.48% (SD = 22.14%) < p95 73.09%
System
6.52%
CPU percentiles
CPU usage percentiles
p50
25.41%
p95
73.09%
p99
95.01%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
7 hosts
mean time
0.31s
Memory used percentage
Percentage of memory used
p5 8.62% < mean 21.62% (SD = 13.25%) < p95 50.68%
Memory available percentage
Percentage of available memory
p5 49.32% < mean 78.38% (SD = 13.25%) < p95 91.38%
Max host memory used
Maximum memory usage percentage across all hosts
max 67.28%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 39.26%
Memory growth rate
Rate of memory growth over time
growth 572.09MB/s
Disk read throughput
Disk read throughput in MB/s
0.33MB/s
Disk write throughput
Disk write throughput in MB/s
656.66MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /
0/25hosts
Mount Point /boot
0/2hosts
Mount Point /efi-boot
0/18hosts
Mount Point /etc/hostname
0/33hosts
Mount Point /etc/hosts
0/33hosts
Mount Point /etc/resolv.conf
0/33hosts
Mount Point /nix/store
0/25hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
2.79
5 min
2.80
15 min
2.77
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
5.08%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 4.9359% (SD = 10.0112%) < p95 21.04%
60 second average
4.8324%
300 second average
5.2427%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 16.4249% (SD = 16.6817%) < p95 45.23%
60 second average
15.9794%
300 second average
15.6634%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 0% < mean 15.521% (SD = 16.169%) < p95 43.46%
60 second average
15.0818%
300 second average
14.5791%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 26.38% (SD = 21.11%) < p95 67.24%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 459.97 KiB < mean 559.66 KiB (SD = 85.98 KiB) < p95696.83 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 32.29 threads (SD = 12.41 threads) < p95 49 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 84.63 file descriptors (SD = 29.45 file descriptors) < p95 123 file descriptors

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
Thu, 19 Mar 2026 01:05:33 UTC
Peer count
1
Peer count at end
1
Behaviours
  • default (1 agent)
Holochain version
0.6.1-rc.3
Wind Tunnel version
0.6.0
Run ID
zome_call_single_value_23274364855
Call timing
The time taken for the call to complete.
mean 0.00495s (SD = 0.06188s) p50 0.002353s p95 0.003756s p99 0.004744s
Call rate
The number of zome calls completed per second.
mean 1974/s
Error count
The number of errors accumulated during the run.
0
Host Metrics
User CPU usage
CPU usage by user space
9.80%
Network receive rate (primary)
Rate of bytes received on primary network interface
p5 17 B/s < mean 18.81 KiB/s (SD = 80.12 KiB/s) < p95179.08 KiB/s
Network send rate (primary)
Rate of bytes sent on primary network interface
p5 9 B/s < mean 622 B/s (SD = 1.77 KiB/s) < p957.45 KiB/s
Total bytes received
Total bytes received on primary network interface
count
6.06 MiB
mean
18.81 KiB/s
Total bytes sent
Total bytes sent on primary network interface
count
200.55 KiB
mean
622 B/s
CPU spike anomaly
CPU spike anomaly was detected
NotDetected
Memory leak anomaly
Memory leak anomaly was detected
Detected

Warning Memory growing at 227.69 MB/s

Disk full anomaly
Disk full anomaly was detected
NotDetected
Swap thrashing anomaly
Swap thrashing anomaly was detected
NotDetected
System overload anomaly
System overload anomaly was detected
NotDetected
Additional Host Metrics
Hidden by default. Click to toggle visibility.
CPU usage
Total CPU usage and kernel CPU usage
Total
p5 0.37% < mean 14.83% (SD = 8.12%) < p95 24.72%
System
5.03%
CPU percentiles
CPU usage percentiles
p50
13.09%
p95
24.72%
p99
47.65%
CPU usage above 80%
Number of hosts above 80% CPU and mean time spent above threshold for those hosts
count
0 hosts
mean time
0.00s
Memory used percentage
Percentage of memory used
p5 23.2% < mean 27.72% (SD = 1.78%) < p95 29.98%
Memory available percentage
Percentage of available memory
p5 70.02% < mean 72.28% (SD = 1.78%) < p95 76.8%
Max host memory used
Maximum memory usage percentage across all hosts
max 27.72%
Max host swap used percentage
Maximum swap space usage percentage across all hosts
max 0.00%
Memory growth rate
Rate of memory growth over time
growth 227.69MB/s
Disk read throughput
Disk read throughput in MB/s
0.00MB/s
Disk write throughput
Disk write throughput in MB/s
3.62MB/s
Disk space utilization risk
Number of hosts nearing disk space capacity by mount point
Mount Point /etc/hostname
0/1hosts
Mount Point /etc/hosts
0/1hosts
Mount Point /etc/resolv.conf
0/1hosts
System load average
System load averages over 1, 5, and 15 minutes. This is an unnormalised value not divided by number of CPUs, so it is only meaningful if all machines have the same core count.
1 min
1.26
5 min
0.60
15 min
0.24
CPU overloaded hosts
Percentage of hosts that experienced CPU overload
0.00%
CPU pressure
CPU pressure over 10, 60, and 300 second averages
10 second average
p5 0% < mean 0.0179% (SD = 0.0634%) < p95 0.2%
60 second average
0.0124%
300 second average
0.0015%
Memory pressure some
Memory pressure (some tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
Memory pressure full
Memory pressure (all tasks stalled) over 10, 60, and 300 second averages
10 second average
p5 0% ≤ mean 0% (SD = 0%) ≤ p95 0%
60 second average
0.0000%
300 second average
0.0000%
I/O pressure some
I/O pressure (some tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 3.14% < mean 26.0909% (SD = 13.9127%) < p95 39.42%
60 second average
21.3944%
300 second average
9.4979%
I/O pressure full
I/O pressure (all tasks stalled) over 10, 60 and 300 second averages
10 second average
p5 3.12% < mean 25.8226% (SD = 13.8104%) < p95 39.03%
60 second average
21.1694%
300 second average
9.3941%
Holochain process CPU usage
CPU usage by Holochain process
p5 0% < mean 11.02% (SD = 5.31%) < p95 20.9%
Holochain process memory (PSS)
Proportional Set Size memory of Holochain process
p5 253.45 KiB < mean 253.83 KiB (SD = 13.35 KiB) < p95257.63 KiB
Holochain process threads
Number of threads in Holochain process
p5 1 threads < mean 10.82 threads (SD = 3.65 threads) < p95 12 threads
Holochain process file descriptors
Number of file descriptors used by Holochain process
p5 0 file descriptors < mean 48.38 file descriptors (SD = 19.43 file descriptors) < p95 72 file descriptors