I’d asked about using a VPS to get better routing to my homelab in this post: https://lemmy.world/post/1424540
I’ve narrowed down my problem- if i use a subdomain in my caddyfile, performance is 1/3 or worse compared to just the root.
example.com {reverse_proxy 192.168.1.57}
will saturate my gigabit lan connection at 980ish. On a 5gUW connection i get my advertised 50 mbit or more
librespeed.example.com {reverse_proxy 192.168.1.57}
I get 220-250 megabits on my internal lan. The same 5gUW connection will only get 7 or 8 mbit.
It’s strange to me that everything seems to work just fine, but it’s just slow. Anyone got any ideas?
I can’t remember if it’s enabled by default or not, but it’s easy enough to enable pprof and get a helpful performance profile from /debug/pprof. See https://caddy.community/t/hangs-on-reload/12010/18 for an example.
I’ve found that even being unfamiliar with the codebase, it’s often pretty easy to identify what part of the call stack is being slow and file a very useful performance but report in GitHub. Check out the profile and see if it leads to any obvious conclusions about why domains are so much slower. There may be some function that’s trivial to cache the results of that brings things back to the expected performance.
The profiles were totally different- because the subdomain uses HTTP/3 via the quic-go library. Disabling it globally has it working at 100%