Benchmarks & Profiling
Disaggregated memory pool bandwidth, RPC latency, and failover timing
Measurements in Preparation
Formal real-device benchmark measurements for AMEVA-Cluster require a minimum two-device fleet configuration (one master, at least one worker). Measurements are being prepared on the Tailscale-connected Galaxy S25 (master) + Galaxy A35 / A53 (workers) fleet.
Planned measurement axes: TCP memory-read throughput (GB/s), RPC round-trip latency (ms), HMAC-SHA256 Guard authentication overhead (µs), UFS 3.1 flash failover switch time (ms), and peak worker-node RSS overhead (MB).
Planned Measurement Conditions
| Metric | Planned Fleet Config | Conditions | Status |
|---|---|---|---|
| TCP memory-read throughput | S25 (master) + A35 (worker) | Tailscale LAN, 4KB–4MB block sizes, 1 GB transfer | Pending |
| RPC round-trip latency | S25 (master) + A35 (worker) | Loopback vs Tailscale vs Wi-Fi direct, 100 iterations | Pending |
| HMAC Guard authentication overhead | S25 standalone | HMAC-SHA256, 1000 verifications | Pending |
| UFS 3.1 flash failover switch time | S25 (master) | Simulated worker disconnect, mmap streaming activation | Pending |
| Worker-node RSS overhead | A35 / A53 (worker-only) | Idle RAM-cache mode, 300MB guard-band active | Pending |