ERPro-8: below 200 Mbps most likely will work, above 550 Mbps most likely will not work.ER-8: below 160 Mbps most likely will work, above 450 Mbps most likely will not work.ERLite-3 and ERPoe-5: below 60 Mbps most likely will work, above 200 Mbps most likely will not work.While many of the Ookla Engineering team use Ubiquiti Edge Routers, their CPU limits their traffic shaping performance to the following: Very few routers provide the ability to shape a single direction of traffic in software, thus I had to find a solution that could handle bi-directional shaping over 200Mbps. My ISP is notorious for having bufferbloat issues due to the low upload performance, and it’s an issue prevalent even on their provided routers.Īs a result, I needed the ability to shape traffic over 200 Mbps speeds - this prevented me from using MIPS or ARM based routers, as they don’t have the CPU horsepower to route over ~150 Mbps without hardware offload (I was actually using Tomato on an Asus AC68U at the time). The solution is to shape the outbound traffic to a speed just under the sending maximum of the upstream device, so that its buffers don’t fill up. This causes immense network congestion, latency to rise above 2,000 ms., and overall poor quality of internet. We will cover bufferbloat in a later article, but in a nutshell, it’s an issue that arises when an upstream network device’s buffers are saturated during an upload. Instead, I have an asymmetrical plan with 200 Mbps download and 10 Mbps upload - this nuance considerably impacted my network design because asymmetrical service can more easily lead to bufferbloat.
I live in an area with a DOCSIS ISP that does not provide symmetrical gigabit internet - my download and upload speeds are not equal. My daily goals range from designing high performance applications supporting millions of users and testing the fastest internet connections in the world, to squeezing microseconds from our stack - so at home, I strive to make sure that my personal internet performance is running as fast as possible. My name is Brennen Smith, and as the Lead Systems Engineer at Speedtest by Ookla, I spend my time wrangling servers and internet infrastructure.
0 kommentar(er)
