Is this massive difference to be expected?

Submitted ⁨⁨12⁩ ⁨hours⁩ ago⁩ by ⁨Timely_Jellyfish_2077@programming.dev⁩ to ⁨selfhosted@lemmy.world⁩

https://programming.dev/pictrs/image/21070631-606b-4673-9899-92a8bc9dba91.png

I ran OpenSpeedTest from my PC to my Raspberry Pi 4B, both connected via LAN to my WiFi router. The left screenshot shows the speedtest via local_ip:3000, and I’m getting the expected 1 Gbps up/down.

The right screenshot shows the speedtest via speed.mydomain.com. I’m confident that the connection from my PC to my home server is routed internally and not through the internet because my lowest ping to the nearest Speedtest server (my own ISP) on speedtest.net is 6ms, and my internet speed is 100 Mbps up/down. So the traffic must be routing internally.

Is there typically such a massive difference between using http://local_ip:3000 and speed.mydomain.com?

Additional context: The speedtest server is running via Docker Compose. I’m using Nginx (native, not Docker) to access these services from outside my network.

source

Comments

Sort:hotnew top

Overspark@feddit.nl ⁨8⁩ ⁨hours⁩ ago
The difference might be HTTP vs HTTPS. On a Pi the extra CPU load to properly encrypt the HTTPS stream is probably significant.

source
tychosmoose@lemm.ee ⁨5⁩ ⁨hours⁩ ago
The port is forwarded from your router to the pi, right? If so, you could test for the router as the bottleneck using the router’s WAN side IP address as the target.

This should give you a good data point for comparison. If it’s also slow then you can focus on the router performance. Some are slow when doing hairpin NAT.

source
Darkassassin07@lemmy.ca ⁨11⁩ ⁨hours⁩ ago
Looking at openspeedtests github page, this immediately sticks out to me:

Warning! If you run it behind a Reverse Proxy, you should increase the post-body content length to 35 megabytes.

source
- taaz@biglemmowski.win ⁨7⁩ ⁨hours⁩ ago
  Also, proxy_buffering
  
  source
towerful@programming.dev ⁨8⁩ ⁨hours⁩ ago
So you have local DNS set up?
If you ping (or dig) speed.mydomain.local, does it resolve the same address as local_ip?
Considering you are accessing local_ip:3000 and the domain on port 443, there is clearly a firewall somewhere redirecting packets or a reverse proxy on the domain but not on local_ip:3000

Follow the port chain, forwarding, proxying etc. One of those will be bottlenecking. Then figure out why

source
- zlatko@programming.dev ⁨7⁩ ⁨hours⁩ ago
  yeah, traceroute might hint at that, if this is what is going on.
  
  source
LodeMike@lemmy.today ⁨10⁩ ⁨hours⁩ ago
NAT can be expensive. Its relaying through your gateway.

source
breakingcups@lemmy.world ⁨9⁩ ⁨hours⁩ ago

Is there typically such a massive difference between using http://local_ip:3000 and speed.mydomain.com?

Only if they resolve to different addresses.

source