mirror of
https://github.com/tailscale/tailscale.git
synced 2026-11-20 08:41:19 -08:00
The QEMU lab runs on a host that's itself a VM, which distorted latency in particular. ec2.sh manages benchmark instances in the sandbox AWS account (us-west-2; the org's SCP allows only some regions and requires IMDSv2): a key pair, a security group open to this host and between its members, a cluster placement group, and Ubuntu 24.04 instances with IPv6 that install the build tools for their own kernel. Everything is named bradfitz-tswg... and tagged owner=claude-tswg. It writes the hosts file that tailscale.com's lean harness takes in remote mode. To keep costs down, ec2-idle-stop.sh, run every 5 minutes from a systemd user timer on the always-on dev host, stops the instances once nothing has touched ~/.cache/tslinux/ec2/last-used for 30 minutes. ec2.sh and the harness touch it while in use, and "ec2.sh start" brings stopped instances back. First EC2 results (c7i.xlarge pair) are in DESIGN.md: throughput is capped by EC2 at about 7.25 Gbps for both tswg and wireguard-go, with tswg's receiver using up to 17% less CPU per byte; 1.6x the small packets; a quarter of the RTT under load at p50; twice the idle RTT. Updates #426 Signed-off-by: Brad Fitzpatrick <[email protected]> Change-Id: Ibe770a30bea31cb79ac514aeb545f468576b5f05