From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] LibreQoS v1.5-BETA-1 is now available!
Date: Thu, 27 Jun 2024 19:04:03 +0200 [thread overview]
Message-ID: <CAJUtOOiFjL9KbQWciDNjoATpPu0FaaArdBd4LXNA_O-8N4dCzw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]
Hello to all,
After 6 months of development, LibreQoS is pleased to announce the first
beta for LibreQoS v1.5. Our v1.4 (released January, 2024) is now in use by
over 150 ISPs in 22 US states and in 42 countries, shaping over a million
subscribers - reducing network latency via CAKE, and providing extensive
diagnostics and statistics to ISP support staff.
*Get v1.5-BETA-1 here:* https://libreqos.io/#download
LibreQoS v1.5 Features Overview:
✅ *30%+ Performance Improvement*. Large improvements in code efficiency.
LibreQoS can now push 70 Gbit/s on a $1500 AMD Ryzen 9 7950X box with a
Mellanox MCX516A card.
✅ *Intelligent Bin-packing*. Dynamically redistribute load (based on
long-term statistics) to get the most out of all of your CPU cores.
✅ *Flow-Based Analysis*. Flows are tracked individually, for TCP
retransmits, round-trip time, and performance. Completed flows can be
analyzed by ASN, geolocated, or exported via Netflow.
✅ *Unified Configuration System and GUI*. No more separate ispConfig.py and
lqos.conf files - all configuration is managed in one place. The web user
interface now lets you manage the whole configuration, including devices
and network lists.
✅* Support for Newer Linux Enhancements*. LibreQoS can take advantage of
eBPF improvements in the 6.x kernel tree to further improve your
performance - but remains compatible with later 5.x kernels.
✅* Improved CLI tools.* lqtop, a new support tool and more.
Full release notes:
https://github.com/LibreQoE/LibreQoS/releases/tag/v1.5-beta-1
*As always, we appreciate all your support and help, and we are looking
forward to seeing you in our chat: *
https://chat.libreqos.io/join/fvu3cerayyaumo377xwvpev6/
All the best,
Frank
Frantisek (Frank) Borsik
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
[-- Attachment #2: Type: text/html, Size: 3413 bytes --]
reply other threads:[~2024-06-27 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJUtOOiFjL9KbQWciDNjoATpPu0FaaArdBd4LXNA_O-8N4dCzw@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox