dispatch proxy? you mean the SOCKS5/HTTP proxy that balances traffic between multiple internet connections right?
yeah don’t go that route unless one’s on second gen wifi/gsm even then not with a socks5 proxy written in node.js. that’s where haproxy works wonders but If one really wants speed and stability then go with a bonded nic connection.
I know I’ll get flack from our network engineering guys around here for say it like this but Bonding network ports is like RAID 0 for networking. It’s also how one’s cable modem is able to now get 100Gb down when it originally could only do 1Gb then 10Gb. They’re bonding the T1 lines downlink behind the scenes for each extra ~10Gb.
Does require the use of a supporting router but mikrotik is inexpensive and can do these sort of advance things unlike most COTS routers including those “gaming” nighthawk routers. Jim’s also right that there would still be a bottleneck if one is not multihoming across ISP carriers. But that’s not a hard limit either.
The average user who want to dual bond their network can get away with 802.3ad (ie trunking / mode 4 bonding) or even Balance Round Robin (mode 1 bonding) and still use just one isp. The bottleneck at that point becomes one’s modem.
There’s other things that can help speed up one’s networking such as installing a Pi-hole with a good set of blocklists set to deny things like malware, ads, etc. This surprisingly cuts a lot of traffic down since it kills these things before it leaves your network including dns and tcp/udp while also caching within one hop the dns request which is the biggest bottleneck in 99.9% of any network traffic (the other .1% is more complex than the usual web browsing / gaming / daily computing stuff).
Disabling uPNP, DNLA, SMB, using static ip, and cached arp are some others but that’s getting a bit old school. Though some other things one can do is seen in https://wiki.mikrotik.com/wiki/Tips_and_Tricks_for_Beginners_and_Experienced_Users_of_RouterOS which may be geared towards Microtik users; do take a high level approach what they’re presenting.
Point being; don’t use software to solve a problem where hardware would work better.