Earlier testing included irqbalance running from boot for multi-core devices. ( – Appears to now be resolved on master)Ĭurrent testing does not include irqbalance. At the present time (September, 2019) it apparently does not work on master. These effects are not explored in this thread, though they may further limit the performance in your environment.įlow offloading is not enabled in the config. If your traffic consists of a large fraction of small packets (such as VOIP), the PPS (packet-per-second) rate will be much higher for a given bandwidth. This testing uses full (1500 MTU), TCP packets. These multi-stream tests are more stressful than single-stream testing. The standard, 60-second test duration (for an overall 70-second run duration) was used. The three tests shown are tcp_8down, tcp_8up, (with ICMP ping) and RRUL (4 up, 4 down, with 3 UDP ping and ICMP ping). Testing was performed using flent which provides 'stress testing' by using multiple streams. It is your responsibility to use any information provided here to assist you in making your decision. If you have a craptastic ISP, a lossy ISP connection, a flakey cable, hosts pummeling your LAN with broadcast traffic, a different traffic distribution, a poorly implemented router, or any of an uncountable number of other things, the results you see may not meet the levels reported here. Like most benchmarks, the performance you get in your own environment may be different. I won't say that my testing is going to definitively answer those questions, but at least it should be a self-consistent data set. While there's been a lot of individuals testing various routers, the question still always seems to come up, 'What can I expect from Router X?'

Easytether ipk download qca9563