3 ms·
> If you have access to wired, wifi and 4G/5G the correct use of that is to always in every single case to use wired, until it breaks. That's not necessarily t
by toast0 4y ago
> If you have access to wired, wifi and 4G/5G the correct use of that is to always in every single case to use wired, until it breaks.
That's not necessarily the case, unless you define 'it breaks' tautologically.
If you're connecting to a LAN server where your server has 2x1G, but your client has 1x1G, you can transfer data faster if you use wired and wifi.
Same thing if your wired internet connection is bandwidth limited; augmenting with 4G/5G would help transfer data faster. Having access to multiple routes may help in case of congestion or faulty links anywhere on the path (although, of course, there's nothing preventing paths being shared by ISPs on multiple last-mile mediums).
On the other hand, MPTCP is difficult to optimize; high performance tcp stacks arrange for all the packets for a given connection to be received on the same cpu to reduce contention; it's hard to arrange that for the two (or more) underlying connections of MPTCP. It's probably better to do MPTCP to protect reachability rather than to improve bulk transfer rates, IMHO.
- tjoff 4y agoSure, but these are really niche edgecases where you really have to optimize it on a case by case. Augmenting with 4G/5G could really help but before daring to do that you'd really have to make sure that it doesn't incur extra costs or drain the data-plan. And mixing in wifi also begs the question, is this latency bound or not? And do we really want to pollute the spectrum with this high-throughput transfer for a minor speed increase? Potential ruining it for everyone else. To make it sensible the server would also need 2x1G which is already very very niche and if it was a considered usecase you'd probably opt for 10G anyway. In the vast majority of cases and probably the only sensible defaults would be wired > wifi > 4G/5G.