I'm noticing that coder ssh work and ssh coder.work take longer than I'd expect before the prompt is available. There's ~1 second of extra overhead.

Just to confirm that there's nothing odd with my network, I took a Wireshark capture and have attached the CSV here: wireshark.csv

I don't see anything out of the ordinary, there's just WebSocket chatter going back and forth until we establish DTLS ~1 second later.

For comparison, here is a timing of SSH into a coder workspace, and a VM running on the same NAS.

❯ time ssh coder.work echo hi; time ssh vm echo hi
hi
ssh coder.work echo hi  0.01s user 0.01s system 0% cpu 1.641 total
hi
ssh vm echo hi  0.14s user 0.01s system 45% cpu 0.337 total

And it doesn't really have to be across the network either, I see the same with Coder running in Docker on a local machine.