IntenseWebs/LibreQoS
3
0
Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2024-12-01 20:19:07 -06:00
Code Issues Packages Projects Releases Wiki Activity
b88f5af477
LibreQoS/v0.9
History
Robert Chacón c9871b9ce4
Create README.md
2022-09-07 11:05:39 -06:00
..
Integrations Update uispImport.py 2021-10-29 08:22:09 -06:00
xdp-cpumap-tc@f44cbf31b5 updating xdp-cpumap-tc 2021-07-02 16:32:23 -06:00
AccessPoints.csv Add files via upload 2021-07-01 23:54:08 -06:00
ispConfig.py Update ispConfig.py 2021-10-29 08:21:49 -06:00
LibreQoS.py Update LibreQoS.py 2021-10-13 06:58:57 -06:00
README.md Create README.md 2022-09-07 11:05:39 -06:00
scheduled.py Add files via upload 2021-07-01 23:54:08 -06:00
Shaper.csv Add files via upload 2021-07-01 23:54:08 -06:00

README.md

v0.9 (IPv4) (Stable)

  • Released: 11 Jul 2021

Features

  • XDP-CPUMAP-TC integration greatly improves throughput, allows many more IPv4 clients, and lowers CPU use. Latency reduced by half on networks previously limited by single-CPU / TC QDisc locking problem in v.0.8.

  • Tested up to 10Gbps asymmetrical throughput on dedicated server (lab only had 10G router). v0.9 is estimated to be capable of an asymmetrical throughput of 20Gbps-40Gbps on a dedicated server with 12+ cores.

  • MQ+HTB+fq_codel or MQ+HTB+cake

  • Now defaults to 'cake diffserv4' for optimal client performance

  • Client limit raised from 1,000 to 32,767

  • Shape Clients by Access Point / Node capacity

  • APs equally distributed among CPUs / NIC queues to greatly increase throughput

  • Simple client management via csv file

Considerations

  • Each Node / Access Point is tied to a queue and CPU core. Access Points are evenly distributed across CPUs. Since each CPU can usually only accommodate up to 4Gbps, ensure any single Node / Access Point will not require more than 4Gbps throughput.

Limitations

  • Not dual stack, clients can only be shaped by IPv4 address for now in v0.9. Once IPv6 support is added to XDP-CPUMAP-TC we can then shape IPv6 as well.

  • XDP's cpumap-redirect achieves higher throughput on a server with direct access to the NIC (XDP offloading possible) vs as a VM with bridges (generic XDP).