IntenseWebs/LibreQoS
3
0
Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2024-11-24 09:10:16 -06:00
Code Issues Packages Projects Releases Wiki Activity
912099cf3d
LibreQoS/old/v0.9
History
Dave Täht 9e984b1216 Major move around of every thing 
Clean up old versions
2022-12-07 11:04:54 -08:00
..
Integrations Major move around of every thing 2022-12-07 11:04:54 -08:00
xdp-cpumap-tc@f44cbf31b5 Major move around of every thing 2022-12-07 11:04:54 -08:00
AccessPoints.csv Major move around of every thing 2022-12-07 11:04:54 -08:00
ispConfig.py Major move around of every thing 2022-12-07 11:04:54 -08:00
LibreQoS.py Major move around of every thing 2022-12-07 11:04:54 -08:00
README.md Major move around of every thing 2022-12-07 11:04:54 -08:00
scheduled.py Major move around of every thing 2022-12-07 11:04:54 -08:00
Shaper.csv Major move around of every thing 2022-12-07 11:04:54 -08:00

README.md

v0.9 (IPv4) (Stable)

  • Released: 11 Jul 2021

Installation Guide

Best Performance, Bare Metal, IPv4 Only:

Good Performance, VM, IPv4 Only:

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).