Cake VS LibreQoS

This is why 90-99% of our builds are done with Cake. It isolates all of it and you can run the build locally if you want.

A good starting point of you want to get started with Cake is our website at https://cakebuild.net/

I don't think it will get too much confusion, but there is a build system called Cake: https://cakebuild.net/

You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?

NAnt was quite a popular build tool used by projects of all sizes targeting .NET Framework on Windows. I have written many complex build systems using NAnt in the past. But XML based DSL was quite clunky to use and maintain. Besides, it was always a daunting task to explain to a new dev on the team. With .NET Core/.NET becoming a cross-platform framework, CAKE and FAKE gained a lot of adoption providing a C# and F# based DSL for build tasks accordingly.

Cake (C# Make) - simple, easy to set up, and with a lot of extensions scripting with C#.

I got the example and the answer I needed on this thread: https://github.com/cake-build/cake/discussions/3564

For those not familiar with it, Cake is a build automation system with a C#-based DSL. It is based on the concept of tasks, which are small units of work, like restoring packages, building, or testing, which can have dependencies on, or trigger, other tasks.

Just a note: there's already a very active community of the same name for the build utility Cake.

Looks interesting! Although the name clashes with Cake (C# Make) project which could be confusing - https://cakebuild.net/

Sorry, I think you are thinking of something else. Maybe a railroad crossing (:-))

Joking aside, the https://www.waveform.com/tools/bufferbloat test looks to see if the networking software is working correctly by putting a large load on the network, and then seeing if other streams are affectec by the overload.

The example on the https://libreqos.io/ home page is of

fq_codel was successfully offloaded in a few products, however, no offload here, just a xeon with a ton of cores and a big L3. On the libreqos case we leveraged some ebpf to do packet steering in what we call the heimdal bridge, and also kathie nichol´s wonderful passive ping concept: https://github.com/thebracket/cpumap-pping

src here: https://github.com/LibreQoE/LibreQoS/

You can get a transparent high speed bridge with shaping capability up pretty rapidly with supported hardware.

I still long for an ethernet card that can do a trie lookup natively! The flamegraphs are mostly getting the right packet to the right cpu, still.

That's doable. The HOA doesn't sell internet. Just pays for a Wi-Fi network that happens to reach you.

I'd advice two high performance dishes (dishes are known to fail and support is an issue so one on standby while waiting) and a business connection. You'll need a third party router with fair queuing, protocol and service speed shaping etc etc. I'm sure both openwrt and opnsense will do. But check this out https://libreqos.io/

Still, ya know, a modernized kernel on the devices is a start, better wifi, also, and if they do get arround to adding at the very least driver support for the linux BQL or AQL subsystems, and apply fq_codel, or cake, they could certainly manage the uplink better. At the higher rates supplied by the link, the wifi becomes the bottleneck for which solutions appeared in the Linux kernel in 2016. There has been some good research on actively managing the link via the sqm-autorate project, and multiple middleboxes such as those from preseem (fq_codel), and my own libreqos.io (cake) , might be able to manage the downlink better with the addition of link level stats, at very minimal CAPEX per subscriber.

Also, people would notice starlink going to hell less often if starlink would just deploy libreqos.io.

With dual 2.5 Gb/s and Alder Lake single-thread perf, I was thinking high-end latency-optimized QoS/Firewall for gigabit internet. CAKE and LibreQoS would love this thing.

It is so wonderful to see so many happy SQM users all over the world. That said, do you think NBN might consider installing libreqos.io to benefit all their other users one day?

I am curious as to the availability and functionality these days of the fq_codel option on the eero 6 and eero 6 business? When I last paid attention about a year ago ( https://www.reddit.com/r/eero/comments/u7xm83/gen_2_sqm_vs_gen_3_sqm_stick_with_gen_2_if_you/ ) only the gen2 had cake, and a lot of folk struggled with correct behaviors at +500Mbit with the 6's implementation of fq_codel. (The +500Mbit problems kind of indirectly spawned the libreqos.io project, which pushes the inbound shaping to a middlebox at the ISP) Anyway, did it get better? Does RFC3168 style ecn work on the wifi?

You probably already know this, but the team behind Cake SQM are pushing to get ISPs to implement the free LibreQoS on their side, so that many more users could benefit from SQM: https://libreqos.io/