DAMM Profiling Report

Load and resource use, rendered plainly.

This page collects the current local control-plane benchmark and the most recent live host workload artifact. It is meant to answer the first performance questions without forcing the operator to open raw JSON by hand.

Enrollment Profiling

Control-plane throughput and memory shape

These figures come from the enrollment benchmark harness. They describe the current local control-plane path, not an end-to-end internet benchmark.

Enrollments / sec
331.90
20 enrollments at concurrency 4
Avg ms / enroll
3.01
total duration 60.26 ms
Peak RSS
71.39 MiB
heap 7.68 → 9.23 MiB
CPU user
101.17 ms
CPU system
16.59 ms
Base URL
http://127.0.0.1:35475
Source: data/benchmark-enroll-quality.json · created 2026-04-20T16:48:32.472Z
Tunnel Workload

Bidirectional transfer over the live tunnel

These figures come from the host workload harness. They show meaningful application traffic over the WireGuard tunnel, not just handshake or ICMP success.

Payload
8 MiB
app port 18080
Left fetched right
5.69 MiB/s
1.41 s total
Right fetched left
15.82 MiB/s
0.51 s total
Left remote IP
10.231.0.2
Right remote IP
10.231.0.1
Integrity
SHA-256 verified
both directions matched after transfer
Source: data/host-workload-hub2-hyle.txt
Interpretation

What these numbers do and do not mean

A good profiling surface should sharpen judgment rather than inflate confidence. The enrollment profile is a local control-plane measure. The workload profile is a controlled-host tunnel measure. Neither should be mistaken for a promise about global user experience under hostile internet conditions.

Generated at 2026-05-04T11:19:57.107Z from revision dc8bf8e.